SOA Worst Practices, Volume I: How to Prevent your SOA from Being DOA

SOA Worst Practices, Volume I: How to Prevent your SOA from Being DOA
Tuesday, 30th November 1999
Published by:

SOA Worst Practices, Volume I: How to Prevent your SOA from Being DOA

We'll share with you the thinking behind these ideas, why they failed, and better approaches that can help you achieve a more successful outcome. (In other words, you will be smarter after reading this. Really.) Some of the things you'll learn:

Why service re-use, not the number of Web services, is the true indicator of SOA value
Why standard SOAP stacks are key to performance
When to build an SOA and the business benefits
How to build an SOA by adding a wrapper to existing applications
Why an XML firewall an SOA does not make
Why it's important to understand the purpose and true benefits of an SOA before moving forward
What key business rules an SOA strategy should address
Why SOA does not require a "rip-and-replace" approach
Why cloning and reconfiguring applications is not the way to go
Why you should be careful about sharing your WSDL
Why your partners can be your best allies when it comes to securing your schema validation

Perhaps you are considering adopting an SOA. Or maybe you are already far down the path of your first. Either way, you will want to keep this guide handy. There's bound to be a worst practice here that you (or a "friend") were tempted to try.

» Get this free white paper now! «

IT Categories

» Computers
» Data Management
» Information Technology
» Internet
» Network Communications
» Security
» Software and Development
» Storage