SOA Patterns

Summary

SOA Patterns provides architectural guidance through patterns and antipatterns. It shows you how to build real SOA services that feature flexibility, availability, and scalability. Through an extensive set of patterns, this book identifies the major SOA pressure points and provides reusable techniques to address them. Each pattern pairs the classic problem/solution format with a unique technology map, showing where specific solutions fit into the general pattern.

About the Technology

The idea of service-oriented architecture is an easy one to grasp and yet developers and enterprise architects often struggle with implementation issues. Here are some of them:

• How to get high availability and high performance
• How to know a service has failed
• How to create reports when data is scattered within multiple services
• How to make loose coupling looser
• How to solve authentication and authorization for service consumers
• How to integrate SOA and the UI

SOA Patterns provides detailed, technology-neutral solutions to these challenges, and many others, using plain language. You'll understand the design patterns that promote and enforce flexibility, availability, and scalability. Each of the 26 patterns uses the classic problem/solution format and a unique technology map to show where specific solutions fit into the general pattern.

The book is written for working developers and architects building services and service-oriented solutions. Knowledge of Java or C# is helpful but not required.

Purchase of the print book comes with an offer of a free PDF, ePub, and Kindle eBook from Manning. Also available is all code from the book.

Table of Contents

PART 1 SOA PATTERNS

1. Solving SOA pains with patterns
2. Foundation structural patterns
3. Patterns for performance, scalability, and availability
4. Security and manageability patterns
5. Message exchange patterns
6. Service consumer patterns
7. Service integration patterns

PART 2 SOA IN THE REAL WORLD

8. Service antipatterns
9. Putting it all together—a case study
10. SOA vs. the world