Architecture for the Agile Enterprise: The Role of Events and ESB’s

1. Architecture for the Agile Enterprise:The Role of Events and ESB’s June 7, 2004 Ron Rasmussen VP Product Development KnowNow Inc. www.knownow.com ron@knownow.com

2. Bridging the gap • Businesses need to be more responsive and agile • Silo’s within enterprises and across partners need to be bridged • Information is changing at an increasing rate • Existing approaches are limited and cannot scale • Batch, Request-Reply, Messaging, EAI, data warehouse, etc. • New solutions have emerged • Enterprise Service Buses (ESB), Event Driven Architectures (EDA), Service Oriented Architectures (SOA)

3. Screen scrape Message queue Down- load file Sockets Screen scrape Screen scrape Down- load file Trans- action file Trans- action file CICS gateway Sockets RPC ORB Message ORB Message queue APPC Trans- action file Trans- action file HTTP HTTP Message queue CICS gateway Screen scrape RPC Down- load file Message APPC Integration Depends On Middleware- The mess created Original Source: Gartner HTTP Modifications: KnowNow

4. Composite Applications Network is the Bus Event Management Publish/Subscribe Many-To-Many Message Routing Message Queuing Transformation Logging Provisioning Event Management Publish/Subscribe Services Service Oriented Architecture Users Enterprise Service Bus

5. EAI CRM ERP Task Based Internet Task Based Request Response Request Response Legacy Departmental Systems ESB Services Oriented Architecture Problem Solving Ad Hoc Extended Enterprise Event Driven Architecture Large Monolithic Systems of Record

6. Key Event Driven Architecture Characteristics • Decoupled communication across the enterprise • No need to know all the recipients of the message • Allows business units to react in new ways without changing event sources • Many-to-many • N-Publishers, M-Subscribers • Degenerate case is 1-to-1 messaging • Dynamic, parallel, and asynchronous • Extends existing systems when they exist • EAI, ESB’s, etc. • Act as a lightweight ESB, EAI if they do not exist • Optimized for events – asynchronous decoupled delivery of events from 1 to 10’s of thousands of subscribers

7. KnowNow Event Management Unique Additions • Meets all the characteristics of an event router for an EDA • Utilize HTTP as core native protocol • Makes KnowNow an “Internet EDA” and a lightweight “Internet Service Bus” • Transparently extends architecture outside the enterprise – beyond the firewall • Why limit next generation architectures to the bounds of your enterprise? It’s not the way your business works so why build in such a limitation? • Desktops are first class citizens • Desktop applications, shrink wrapped or custom, participate in events and bus’s are extended to the desktop. • J2EE/.NET Architecture agnostic • Native .NET, JAVA, C++, HTTP POST interfaces • Designed from inception for internet scale event routing

8. Summary • Businesses driving latency down • More business, more profitable • Events drive business process, automating events puts you on a path of agility • Existing middleware and approaches cannot keep up with the speed of business • ESB’s with events and Event Driven Architectures are well suited to delivering agility • KnowNow is uniquely positioned to enable event driven systems in a simple non-disruptive way within and between enterprises

9. Architecture for the Agile EnterpriseRole of Events and ESB June 7, 2004 Ron Rasmussen VP Product Development KnowNow Inc. www.knownow.com ron@knownow.com