Click Here

Continuing my business-driven architecture series, I just published an Event-Driven Architecture Overview for the PSGroup Research Service. In the overview, I explain key event concepts, walk through event processing flows, and identify the major implementation components of an event-driven architecture. This post excerpts the core of the paper. If you would prefer the full report, go here (free with registration). For those unfamiliar with business-driven architecture, I believe the most viable, agile architectures will be comprised of a secure email blend of architecture strategies, including (but not limited to) service-oriented architecture, event-driven architecture, process-based architecture, federated information, enterprise integration and open source adoption. How you blend, depends on your business. Before I jump into the excerpt, I want to touch on the relationship between service-oriented architecture and event-driven architecture. I believe that SOA and EDA are peers and complements. So, I disagree with the SOA evangelists who say EDA is merely a subset (child) of SOA. On the SOA and EDA are complements point, I see two distinct interactions: Event-Driven SOA. In the first interaction, the occurrence of an event (a notable thing that happens inside or outside your business) can trigger the invocation of one or many services. Those services may perform simple functions, or entire business processes.

Caspar de Bono on his father, Edward, who keeps his things sorted into piles, by importance: He's very frugal in his day-to-day needs, he doesn't splash his money about and he keeps absolutely everything. His mantelpiece is crammed with clockwork teeth and plastic dinosaurs. Toy shops are a passion; everywhere he goes he seeks them out and emerges with a new toy, something with a trick or a dual purpose which fascinates him. Though his surroundings look chaotic, his life is very structured. His flat is filled with piles of stuff, login failure but on top of each is a white tile with a number, rating it in importance . More how we work .

Click Here

Continuing my business-driven architecture series, I just published an Event-Driven Architecture Overview for the PSGroup Research Service. In the overview, I explain key event concepts, walk through event processing flows, and identify the major implementation components of an event-driven architecture. This post excerpts the core of the paper. If you would prefer the full report, go here (free with registration). For those unfamiliar with business-driven architecture, I believe the most viable, agile architectures will be comprised of a blend of architecture strategies, including (but not limited to) service-oriented architecture, event-driven architecture, process-based architecture, federated information, enterprise integration and open source adoption. How you blend, depends on your business. Before I jump into the excerpt, I want to touch on the relationship between service-oriented architecture and event-driven architecture. I believe programs affiliate marketing that SOA and EDA are peers and complements. So, I disagree with the SOA evangelists who say EDA is merely a subset (child) of SOA. On the SOA and EDA are complements point, I see two distinct interactions: Event-Driven SOA. In the first interaction, the occurrence of an event (a notable thing that happens inside or outside your business) can trigger the invocation of one or many services. Those services may perform simple functions, or entire business processes.