SOA seems to say that all of the business of the company becomes a distributed scalable service collection based on a standard service interface platform. It seems to be a bit winding ... My understanding, the first is to put all the business in a unified interface platform, making services, so that users use it easier. This service is easy to expand, it is easy to keep with the times. Distributed, the different services can be done by different entities, and the final summary will be given to the user on the interface platform. This thing seems to look more than the giant ha, enterprise application, is still a bit interesting, it seems to be a comparative strength.
SOA is a big architecture, while WebService is just a specific technology. SOA can be implemented with WebService or not. However, I think SOA's design is still drawn on the concept of WebService. However, I saw the second article and hared. It seems that the software architecture is really long.
Article link:
Next generation software architecture - Soa http://dev.9cbs.net/develop/Article/84/84692.shtm
Why don't you make SOA simple? http://dev.9cbs.net/Article/84/84687.shtm
Resources · Jini technology, one of the earliest SOA implementations: http://www.jini.org · Jee specification: http://java.sun.com/j2ee/download.html#PlatformSpec · Learn .NET : Http://msdn2.microsoft.com/en-us/library/ms310245 (En-US, MSDN.10) .aspx · http://www.uddi.org UDDI Agreement · Create SOA Preparation: HTTP: / /weblog.infoworld.com/techwatch/archives/004644.html · Java business integrates for Java applications (specifically refer to SOA-based applications). This is more formal, so it allows vendors to provide tools and frameworks based on standards to achieve ultimate interactivity. Many failed to fail is because of the lack of these support: http://www.jcp.org/en/jsr/detail? Id = 208 · http://ws.apache.org/Axis/ Open source JEE web service implementation - Apache Axis
