Top Ten Enterprise Service Bus (ESB) Myths

1
Top Ten Enterprise Service Bus (ESB) Myths
Gordon Van Huizen CTO, Sonic Software March 17,
2005
2
Sonic Software
Inventor and Leading Provider of the Enterprise
Service Bus (ESB)

• Recognized Inventor of the ESB
• Enterprise messaging (1 JMS product)
• Standards Contributor/Influencer
• Established 700 Customers, 40 OEM/ISV
  partnerships
• Extensive SI Partner Support
• Independent Operating company of
• Progress Software (NASDAQ PRGS)
• 363M sales, over 180M in cash
• consistent double digit revenue and profit
  growth
• Distribution in 65 countries
• 24x7 world-wide support
• Experienced Enterprise projects deployed in
• - Finance Banking
• - Telco
• - Retail
• - Government
• - Transportation and Logistics

3
About Todays Speaker
Gordon Van Huizen

• CTO, Sonic Software
• Background
• 24 years of software industry experience
• Formerly VP, Product Management at Sonic
• Brought worlds first ESB to market
• Former Director of Engineering for BEA WebLogic
  Server
• Has lead development of Internet applications,
  application servers and middleware since 1996

4
The SOA Vision
5
ESB Role in Enterprise SOA

• Connect services through enterprise-grade
  communications

• Mediate service interactions through
  metadata-driven configuration

• Host integration functions as intermediary
  services

• Provide centralized service management and
  monitoring

SCM
Integration Broker
CRM
Tracking Service
Adapter
Adapter
Order Entry
ERP
CRM
SCM
Partner
Finance
Enterprise
6
1 ESB is just a new name for EAI.
ESBs provide general-purpose SOA infrastructure
that can be used for many applications, including
EAI.
7
2 ESBs compete with J2EE application servers.
ESBs complement app servers in an Enterprise SOA
environment, by offering service mediation,
intelligent routing, distributed communication
and service management.
8
3 I dont need an ESB if Im using Web services.
ESBs make it practical to deploy an Enterprise
SOA through increased reliability, security and
scalability in addition to post-deployment
flexibility and service management.
9
4 An ESB is simply an abstract concept or
design pattern.
An ESB provides a specific set of capabilities,
brought together in a coherent, unified
service-oriented architecture.
10
5 ESBs are simply message-oriented middleware
with a new marketing spin.
In addition to their messaging layer, ESBs
contain a full distributed services architecture,
with the ability to host, configure, mediate,
orchestrate and manage services.
11
6 ESBs will be obsolete once BPEL and the WS-
standards are complete.
BPEL and the WS- standards will further
interoperability between ESBs and application
platforms, but do not remove the need for service
mediation, routing and management.
12
7 Microsoft is building an ESB with their
Indigo project.
Indigo will make it easier to build
message-driven applications in .NET but doesnt
appear to include the configurable
intermediaries, dynamic distributed deployment or
management capabilities found in an ESB.
13
8 An ESB container can be implemented using an
EJB container.
ESBs require service containers that are
lightweight, dynamically configurable and support
event-driven services.
14
9 ESBs offer yet another proprietary middleware
stack.
ESBs are based on XML and Web services standards,
and ESB vendors are implementing and contributing
to the next generation of standards for further
interoperability and openness.
15
10 ESBs are only useful for departmental
applications.
Hundreds of ESBs have been deployed around the
world for mission-critical enterprise and B2B
systems.
16
CONNECT EVERYTHING. ACHIEVE ANYTHING.