Enterprise Service Oriented Architectures: Concepts, Challenges, Recommendations (The Enterprise Series)
|
| List Price: | $84.95 |
| Price: | $38.30 & eligible for FREE Super Saver Shipping on orders over $25. Details |
Availability: Usually ships in 24 hours
Ships from and sold by Amazon.com
33 new or used available from $24.37
Average customer review:Product Description
Conventional wisdom of the "software stack" approach to building applications may no longer be relevant. Enterprises are pursuing new ways of organizing systems and processes to become service oriented and event-driven. Leveraging existing infrastructural investments is a critical aspect to the success of companies both large and small. Enterprises have to adapt their systems to support frequent technological changes, mergers and acquisitions. Furthermore, in a growing global market, these systems are being called upon to be used by external business partners. Technology is often difficult, costly and complex and without modern approaches can prevent the enterprise from becoming agile.
Enterprise Service Oriented Architectures helps readers solve this challenge in making different applications communicate in a loosely coupled manner. This classic handbook leverages the experiences of thought leaders functioning in multiple industry verticals and provides a wealth of knowledge for creating the agile enterprise.
In this book, you will learn:
• How to balance the delivery of immediate business value while creating long-term strategic capability
• Fundamental principles of a service-oriented architecture (find, bind and execute)
• The four aspects of SOA (Production, Consumption, Management and Provisioning)
• How to recognize critical success factors to implementing enterprise SOAs
• Architectural importance of service registries, interfaces and contracts
• Why improper service decomposition can hurt you later rather than sooner
• How application design and integration practices change as architects seek to implement the "agile" enterprise
About the Authors
James McGovern is an enterprise architect for The Hartford. He is an industry thought leader and co-author of the bestselling book: A Practical Guide to Enterprise Architecture.
Oliver Sims is a recognized leader in the architecture, design and implementation of service-oriented and component-based enterprise systems. He was a founding member of the OMG Architecture Board. He was co-author of the groundbreaking book: Business Component Factory.
Ashish Jain is a Principal Architect with Ping Identity Corporation, a leading provider of solutions for identity federation. Prior to joining Ping Identity, he worked with BEA Systems where his role was to assist BEA customers in designing and implementing their e-business strategies using solutions based on J2EE. He holds several industry certifications from SUN and BEA and is also a board member for the Denver BEA User group.
Mark Little is Director of Standards and SOA Manager for JBoss Inc. Prior to this, he was Chief Architect for Arjuna Technologies Ltd and a Distinguished Engineer at Hewlett-Packard. As well as being an active member of the OMG, JCP, OASIS and W3C, he is an author on many SOA and Web Services standards. He also led the development of the world's first standards-compliant Web Services Transaction product.
Product Details
- Amazon Sales Rank: #135865 in Books
- Published on: 2006-04-28
- Number of items: 1
- Binding: Hardcover
- 408 pages
Customer Reviews
Dishonest authors
These folks use my book, "How to Open Locks With Improvised Tools" in their work. They stated that my book was published by Harper Collins in 1997. The first version, "Lock Bypass Methods" was published in 1998, and the version they cite was published in 2001, by Level Four Publications. The title page, including contact info in my book, is concise and clear. Harper Collins has never touched it. No, they didn't ask permission for use, and there are so many spelling and grammatical errors that it is obvious they cut corners in other places, too. Since they're happy to invent spurious references when the real thing is readily available, I wouldn't hold much faith whatever else they cranked out. I'm sorry my name shows up in their shoddy work.
Disappointed
There were a few decent pieces of information, but overall I was not very impressed. Some of the content was OK, but the grammatical errors and different writing styles made it a very disappointing read. There were four different authors which contributed to the flow problems, and it was obvious that some of the chapters were more poorly written than others. In addition, it didn't seem like anyone even proofed the book. I can understand a few errors, but I found myself re-reading sentence after sentence trying to understand what words were missing, misspelled or out-of-place.
The chapter on transactions was pretty decent. I liked the information on compensating transactions, which I had heard called three phase commit previously. The chapter on UDDI was pretty decent as well. I was disappointed in the last chapter on Event-Driven Architecture. It just seemed to be a hodge-podge catch all of the author's thoughts without much meat.
use BPEL for workflow
This topical book takes us through the many facets of SOA. It can help you understand and implement an SOA redesign of your company's software assets. One of the promises of SOA is that the redesign can start at a higher level. Not at the software or the design of the software per se, but at modelling the workflow and business process management. The book bundles these under the label of "Orchestration" and explains how the Business Process Execution Language (BPEL) offers the expressive power to document them. Actually, BPEL can do more than document. There is a prospect here that BPEL can be used to implement how the workflow proceeds, at the level of Web Services. Of course, the latter still have to be written. The reader needs to appreciate that the bulk of the work resides outside the book's scope, in the coding of those Web Services.
The book shows the considerable potential of SOA.






