Event Driven Architecture Not Your Grandmother's SOA
posted by Anna Mar, February 12, 2011The design principles known as SOA have been around since way back in 2004. Back then, SOA was typically orchestrated centrally. In other words, SOA was used to drive pre-defined business processes.
This old model, often referred to as SOA 1.0, ignors events outside of a static business model. Since everything needs to be modelled ahead of time, SOA 1.0 is not good at dealing with surprise, irregular, random or scheduled enterprise events.
SOA 2.0, often referred to as event driven SOA, adds the ability to accept events, filter them, generate business events and handle with soa services.
SOA 2.0 may handle events such as business events, external events, system events, platform events or events in the component layer.
Don't worry about people stealing your ideas. If your ideas are any good, you'll have to ram them down people's throats.
~ Howard Aiken |
Enterprise Architecture (EA) is supposed to help manage IT risks
— but is it possible that EA itself introduces new risks? |
Recently on Simplicable
Authentication vs Authorizationposted by Anna MarIt is easy enough to confuse authentication and authorization. |
Multifactor Authentication Explainedposted by Anna MarHow to confirm the identity of users and entities. |