I finished reading Enterprise SOA - Service-Oriented Architecture Best Practices (Dirk Krafzig, Karl Banke, Dirk Slama).
It seems to be one of the higher rated SOA books on Amazon. That is why I also read Thomas Erl's SOA (Concepts, Technology, and Design) book.
This book seems to show a little more hands on knowledge and things to watch out for rather than web service specifications. Although SOA is most commonly thought of along with WS-* specifications, SOA can be implemented without web services.
The big benefits I see are reusability and interoperability. Reusability in exposing small functional pieces that can be put together for strategic reasons through an orchestration. Interoperability in exposing siloed pieces of functionality of an organization to allow all the information to work together. By exposing different platforms(Java, .NET, mainframe,...), the organization can more easily build enterprise applications to meet short and long term goals.
Definitions of SOA:
A Service-Oriented Architecture(SOA) is a software architecture that is based on the key concepts of an application frontend, service, service repository, and service bus. A service consistes of a contract, one or more interfaces, and an implementation. (Krafzig, p. 57)
SOA is a form of technology architecture that adheres to the principles of service-orientation. When realized through the Web services technology platform, SOA establishes the potential to support and promote these principles throughout the business process and automation domains of an enterprise. (Erl, p.54)
Some videos:
Subscribe to:
Post Comments (Atom)
2 comments:
Amiable brief and this post helped me alot in my college assignement. Say thank you you on your information.
Amiable fill someone in on and this enter helped me alot in my college assignement. Say thank you you as your information.
Post a Comment