SOA for the confused
posted by Anna Mar, March 24, 2011SOA is not a technology — it is a design methodology.
In recent months I have run across a flurry of misleading articles about SOA. In particular, there seems to be confusion about the relationship between SOA and technologies such as BPM, ESB and Complex Event Processing (CEP).
The confusion is needless because SOA has a pretty simple relationship with these technologies.
SOA and ESB
One of the 9 SOA design principles is loose coupling of services.ESB is the most common way to implement loose coupling for SOA services. The relationship between the two is as simple as that.
SOA and BPM
BPM is a tool that orchestrates business processes. Steps in that process can be completed by a SOA service.
Alternatively, a SOA service could call a BPM to execute a process — but this pattern is less common.
SOA and Complex Event Processing (CEP)
SOA 2.0 is a design approach for Complex Event Processing.Traditional SOA (SOA 1.0) are services are consumed by BPM engines, applications and other services. In other words, SOA 1.0 is centrally orchestrated.
SOA 2.0 (event driven SOA) services are designed to be consumed by events or patterns of events (both unpredictable and scheduled).
|
Take a few minutes to learn about the Zachman Framework — a framework for Enterprise Architecture. |
|
Understand the threats to your organization. |
|
Explaining complex business and technical concepts in layman's terms. |
Recently on Simplicable
| Enterprise Architecture Guideposted by John SpaceyA large collection of enterprise architecture tools. |
| 6 Steps To Business Process Management Successposted by Anna MarWant to automate, monitor, measure and continually optimize your business? You might need BPM. |
| 6 Reasons You Need a SaaS Data Escrow Serviceposted by Anna MarIf you use SaaS you need a data escrow service — here's why. |
| 5 Common Current State Architectural Blueprint Mistakesposted by Anna MarA current state architectural blueprint is essential to your success as an IT organization. After all, you can't effectively manage a complex architecture that's not documented. |
