Note that there are some explanatory texts on larger screens.

plurals
  1. POPractical SOA for a newbie
    text
    copied!<p>I am a total newbie to the world of SOA. As such, I am looking at some "SOA frameworks/technologies", and trying to understand how to utilize them to build a highly scalable (Facebook class) website.</p> <p>There are several "pains" I am trying to solve here:</p> <ol> <li>Composability (+ managing dependencies, Pub/Sub)</li> <li>Language-independence of services</li> <li>Scalability &amp; Performance</li> <li>High availability</li> </ol> <p>I looked into some technologies that answer a subset of the above criteria:</p> <ol> <li><a href="http://incubator.apache.org/thrift/" rel="nofollow noreferrer">Thrift</a> - Facebook's cross-platform RPC platform</li> <li><a href="http://en.wikipedia.org/wiki/Windows_Communication_Foundation" rel="nofollow noreferrer">WCF</a> - supports SOAP, JSON &amp; REST, so it can be considered language-interoperable. Generates <a href="http://en.wikipedia.org/wiki/Web_Services_Description_Language" rel="nofollow noreferrer">WSDL</a> files that can be use to generate java proxies.</li> <li><a href="http://social.msdn.microsoft.com/Forums/en-US/roboticsdss/thread/babf3e90-8196-40b2-a4a1-5f2ecc4e9b47" rel="nofollow noreferrer">Microsoft DSS</a> - just inclued it in my survey, but it doesn't seem relevant as it is highly state-driven and .NET specific.</li> <li>Web Services</li> </ol> <p>Now, I understand how I get some aspects of composability and language-independence out of the above. But, I haven't found much concrete information (not buzz) about how to use the above / other tools for scalability and high availability. So finally I get to my question:</p> <p><strong>How does one leverage SOA technologies to solve the pains I defined above?</strong> Where can I find technical guides for that? I am looking for more than just system diagrams, but rather actual libraries, code samples, APIS...</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload