Top Ten Enterprise Service Bus (ESB) Myths

CONNECT EVERYTHING. ACHIEVE ANYTHING.™

Top Ten Enterprise Service Bus (ESB) Myths

Gordon Van HuizenCTO, Sonic Software

March 17, 2005

2 © 2005 Sonic Software Corporation

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

Sonic SoftwareInventor and Leading Provider of the Enterprise Service Bus (ESB)


About Today’s Speaker

CTO, Sonic Software

Background– 24 years of software industry experience

– Formerly VP, Product Management at Sonic Brought world’s first ESB to market

– Former Director of Engineering for BEA WebLogic Server

– Has lead development of Internet applications, application servers and middleware since 1996

Gordon Van Huizen


The SOA Vision

J2EE App

.NET AppService

Repository

ManagementTools

FirewallApplications

Internalapplications

External applications

Broad-scale interoperabilityModularity / reuse

Incremental deploymentFlexibility

PartnerPortal App

RemoteOffice

RemoteOffice

``Shared ``Key ``Services

.NET App

J2EE App

Legacy App


ESB Role in Enterprise SOA

Provide centralized service management and monitoring

Connect services through enterprise-grade communications Mediate service interactions through metadata-driven configuration Host integration functions as intermediary services


#1: ESB is just a new name for EAI.

#1: ESB is just a new name for EAI.

ESBs provide general-purpose SOA infrastructure that can be

used for many applications, including EAI.

ESBs provide general-purpose SOA infrastructure that can be

used for many applications, including EAI.


#2: ESBs compete with J2EE application servers.

#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.

ESBs complement app servers in an Enterprise SOA environment,

by offering service mediation, intelligent routing, distributed communication and service

management.


#3: I don’t need an ESB if I’m using Web services.

#3: I don’t need an ESB if I’m 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.

ESBs make it practical to deploy an Enterprise SOA through

increased reliability, security and scalability in addition to post-

deployment flexibility and service management.


#4: An ESB is simply an abstract concept or design pattern.

#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.

An ESB provides a specific set of capabilities, brought together in a coherent, unified service-oriented

architecture.


#5: ESBs are simply message-oriented middleware with a new

marketing spin.

#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.

In addition to their messaging layer, ESBs contain a full

distributed services architecture, with the ability to host, configure, mediate, orchestrate and manage

services.


#6: ESBs will be obsolete once BPEL and the WS-* standards are

complete.

#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.

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.


#7: Microsoft is building an ESB with their “Indigo” project.

#7: Microsoft is building an ESB with their “Indigo” project.

Indigo will make it easier to build message-driven applications in .NET

but doesn’t appear to include the configurable intermediaries, dynamic

distributed deployment or management capabilities found in an

ESB.

Indigo will make it easier to build message-driven applications in .NET

but doesn’t appear to include the configurable intermediaries, dynamic

distributed deployment or management capabilities found in an

ESB.


#8: An ESB container can be implemented using an EJB

container.

#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.

ESBs require service containers that are lightweight, dynamically configurable and support event-

driven services.


#9: ESBs offer yet another proprietary middleware stack.

#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.

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.


#10: ESBs are only useful for departmental applications.

#10: ESBs are only useful for departmental applications.

Hundreds of ESBs have been deployed around the world for mission-critical enterprise and

B2B systems.

Hundreds of ESBs have been deployed around the world for mission-critical enterprise and

B2B systems.

CONNECT EVERYTHING. ACHIEVE ANYTHING.

Documents

Top Ten Enterprise Service Bus (ESB) Myths