Comments on: Combining Service-Oriented Architecture and Event-Driven Architecture using an Enterprise Service Bus http://www.complexevents.com/2006/08/29/combining-service-oriented-architecture-and-event-driven-architecture-using-an-enterprise-service-bus/ Applications, products, research, and developments in event processing Tue, 01 Nov 2011 16:49:30 +0000 hourly 1 http://wordpress.org/?v=3.2.1 By: Jack van Hoof http://www.complexevents.com/2006/08/29/combining-service-oriented-architecture-and-event-driven-architecture-using-an-enterprise-service-bus/comment-page-1/#comment-51 Jack van Hoof Tue, 29 Aug 2006 20:38:33 +0000 http://complexevents.com/?p=105#comment-51 Events happening in the real world should be the starting point of a SOA-design. Real-world events are the triggers for the business processes by nature. We at Dutch Railways promote to start with modelling the events. We describe events in canonical formats and we publish the events in a "global dataspace" (implemented by an ESB). We use web services interface technology and an ESB to publish these events and to consume them. In our opinion SOA starts with recognizing the real-world events (what to react on) that will be the basis for defining generic functional building blocks to compose SOA's (how to react; the process). It's a kind of contract-first design. Modelling events is what we call an event-driven architecture (EDA). EDA has affinity with business processes and SOA has affinity with application construction. Taking into account that the EDA approach is an inverse of the well known SOA approach you might say the two paradigms are complements by nature. The layer between the real-world events and artificial IT-systems (SOA) is an EDA. It's the way we obtain the alignment of our business and the supporting IT-systems. <a href="http://soa-eda.blogspot.com" rel="nofollow">Read more...</a> <a href="http://soa-eda.blogspot.com" rel="nofollow">Jack van Hoof</a> Enterprise Integration Architect at Dutch Railways Events happening in the real world should be the starting point of a SOA-design. Real-world events are the triggers for the business processes by nature. We at Dutch Railways promote to start with modelling the events. We describe events in canonical formats and we publish the events in a “global dataspace” (implemented by an ESB). We use web services interface technology and an ESB to publish these events and to consume them. In our opinion SOA starts with recognizing the real-world events (what to react on) that will be the basis for defining generic functional building blocks to compose SOA’s (how to react; the process). It’s a kind of contract-first design.

Modelling events is what we call an event-driven architecture (EDA). EDA has affinity with business processes and SOA has affinity with application construction. Taking into account that the EDA approach is an inverse of the well known SOA approach you might say the two paradigms are complements by nature. The layer between the real-world events and artificial IT-systems (SOA) is an EDA.

It’s the way we obtain the alignment of our business and the supporting IT-systems.

Read more…

Jack van Hoof
Enterprise Integration Architect at Dutch Railways

]]>