architecture for the agile enterprise: the role of events and esb’s
DESCRIPTION
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 [email protected]. Bridging the gap. Businesses need to be more responsive and agile - PowerPoint PPT PresentationTRANSCRIPT
Architecture for the Agile Enterprise:Architecture for the Agile Enterprise:The Role of Events and ESB’sThe Role of Events and ESB’s
Ron RasmussenRon RasmussenVP Product Development
KnowNow Inc.
www.knownow.com
June 7, 2004
Bridging the gapBridging 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)
HTTP HTTP
Integration Depends On MiddlewareIntegration Depends On Middleware- - The mess createdThe mess created
Down-loadfile
Down-loadfile
Down-loadfile
Screen
scrape
Screen
scrape
Screen
scrape
Screen
scrape
Trans-action
file
Trans-action
file
Trans-action
file
Trans-action
file
Messagequeue Message
queue
Messagequeue
Sockets
SocketsORB
Message
RPC
Message RPC
CICS gateway
APPC
APPC
CICS gateway
ORB
Original Source: GartnerHTTP Modifications: KnowNow
Event ManagementPublish/SubscribeMany-To-ManyMessage RoutingMessage QueuingTransformationLogging Provisioning
Service Oriented ArchitectureService Oriented Architecture
Composite Applications
Services
Users
Network isthe Bus
Enterprise Service Bus
Event ManagementPublish/Subscribe
Legacy Departmental
Systems
Event Driven ArchitectureEvent Driven Architecture
CRM
RequestResponse
Task Based
EAI
ERP
Task BasedRequestResponse
ESBServices Oriented
Architecture
Large Monolithic Systems of Record
Problem Solving
Ad HocExtended Enterprise
Internet
Key Event Driven Architecture CharacteristicsKey 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
KnowNow Event Management KnowNow Event Management Unique AdditionsUnique 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
SummarySummary
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
Architecture for the Agile EnterpriseArchitecture for the Agile EnterpriseRole of Events and ESBRole of Events and ESB
Ron RasmussenRon RasmussenVP Product Development
KnowNow Inc.
www.knownow.com
June 7, 2004