SOA Worst Practices Volume I

Make no mistake: SOA can be tricky. Learn from this compilation of "SOA Worst Practices" which traps to avoid. Learn the limits of XML firewalls. Find out how not to fall prey to consultants. Make sure you don't hand out your WSDL to passersby... This wisdom and much, much more from the experts at Actional.

Register to download this white paper for free today.

Note: The items in BOLD are required fields. You must supply a valid email address to complete the registration.


First Name
Last Name
Company
Title
Job Category
Industry
Email
Telephone
Address 1
Address 2
City
Country
State/Prov
Postal Code

SOA Best Practices—Not!

For more than six years, Actional has been at the forefront of SOA technology, working with early adopters and partnering with industry leaders. In that time, we've seen it all—and proudly penned a few of our own SOA best practices. As one might imagine, Actional SOA management solutions have been behind more than one customer's SOA success story.

Best SOA Practices? Your Best Idea Might Actually Be Your Worst SOA Practice

We also realize that knowing what not to do when building a SOA can be just as valuable as knowing what to do. That's why we've created this "worst practices" guide.

In this tutorial, you'll learn about real-life (and real lame) mistakes made by your peers. 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.)

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

If Actional can save even one developer from the SOA Worst Practices Hall Of Shame, then writing this guide will have been well worth the effort.

A Few Thoughts as You Move Ahead

Building a SOA can be challenging, even agonizing. Sometimes ideas that look good on paper are not so good in practice. Many, in fact, actually turn out to be worst practices. But, as this guide illustrates, you can learn a lot from others' mistakes, including:

  • Why Web service reuse, not the number of Web services, is the true indicator of SOA value
  • Why standard SOA SOAP stacks are key to performance
  • When to build a SOA and the business benefits
  • How to build a SOA by adding a Web services wrapper to existing applications
  • Why an XML firewall does not offer sufficient protection for your SOA
  • Why it's important to understand the purpose and true benefits of a SOA before moving forward
  • What key business rules a SOA strategy should address
  • Avoid SOA integration woes: Why SOA shouldn't require a "rip-and-replace" approach
  • Build your SOA services: Why cloning and reconfiguring applications is not the way to go
  • Why, in the case of SOA, WSDL should not be treated lightly
  • SOA security secret: Why your partners can be your best allies when it comes to securing your schema validation

Even more important than learning (tactically) from other people's individual mistakes, an overall study of this tutorial will help you gain the wisdom needed to make better decisions as you embark on your SOA initiative.

For More Information

Want to learn more detailed SOA best practices? Download the free webinar, SOA Governance: Where the Rubber Meets the Runtime