|By Dave Chappell||
|August 31, 2004 12:00 AM EDT||
The past several years have seen some significant technology trends, such as service-oriented architecture (SOA), enterprise application integration (EAI), business-to-business (B2B), and Web services. These technologies have attempted to address the challenges of improving the results and increasing the value of integrated business processes, and have garnered the widespread attention of IT leaders, vendors, and industry analysts. The enterprise service bus (ESB) draws the best traits from these and other technology trends to form a new architecture for integration. The ESB concept is a new approach to integration that can provide the underpinnings for a loosely coupled integration network that can scale beyond the limits of a hub-and-spoke EAI broker.
An ESB is a highly distributed, event-driven, enterprise SOA that is geared toward integration. It is a standards-based integration platform that combines messaging, Web services, data transformation, and intelligent routing to reliably connect and coordinate the interaction of significant numbers of diverse applications across extended enterprises with transactional integrity. An extended enterprise represents an organization and its business partners, which are separated by both business boundaries and physical boundaries. In an extended enterprise, even the applications that are under the control of a single corporation may be separated by geographic dispersion, corporate firewalls, and interdepartmental security policies.
An ESB is designed to be pervasive, meaning that it is capable of spanning the extended enterprise. But an ESB is also pervasive in the sense that it is capable of being used as a general-purpose integration environment that is suitable for any project, no matter how large or how small.
The SOA of the ESB
An ESB is the implementation backbone for a loosely coupled, event-driven SOA that enables a highly distributed universe of named routing destinations across a multi-protocol message bus.
An SOA provides an integration architect with a broad abstract view of applications and integration components to be dealt with as high-level services. Service components in an ESB expose coarse-grained, message-driven interfaces for the purpose of sharing data between applications, both synchronously and asynchronously. In an ESB, applications and event-driven services are connected through the bus as abstract endpoints. These abstract endpoints are tied together in a loosely coupled SOA, which allows them to operate independently from one another. An integration architect uses an ESB to tie together assemblies of abstract endpoints that form composite business processes, or process flows (see Figure 1).
What the endpoints actually represent can be very diverse. For example, an endpoint may represent a discrete operation, like a specialized service for calculating sales tax. The underlying implementation of the endpoint could represent a local binding to an application adaptor, or a callout to an external Web service. The applications and services can be physically located anywhere that is accessible by the bus.
In an ESB, data is passed between endpoints using messages. The coordination of the message passing is done using an ESB concept known as itinerary-based routing. A message itinerary is metadata that gets carried with a message that provides a list of forwarding addresses. The itinerary is a set of instructions telling the ESB invocation framework which endpoints the message needs to be delivered to as it travels from endpoint to endpoint across the bus. Itineraries contribute to the distributed nature of the ESB architecture by eliminating the dependency on a centralized routing engine, which could potentially be a single point of failure. They are intended for relatively finite microflows of messages. Simple branching and merging of routing paths can be achieved through integration patterns that take advantage of specialized splitter and aggregator services. More sophisticated process orchestrations are also possible using specialized orchestration engines that can be layered onto the bus as additional services.
Configuration, Not Coding
The mantra of the ESB is "configuration rather than coding." In an ESB, abstract endpoints, which are accessible through application adapters, message queues, Web services invocations, and a variety of other protocols, are configured through a tool interface rather than coded into applications. It's not that there's anything wrong with writing code, but there's plenty of code to be written elsewhere that doesn't have to do with hard-wiring interdependencies between applications and services.
With its distributed deployment infrastructure, an ESB can efficiently provide central configuration, deployment, and management of services that are distributed across the extended enterprise. Artifacts that affect the behavior of an integration service, such as an XSLT stylesheet that can be used by a data transformation service, are also configurable in an ESB.
The ESB Service Container
The highly distributed nature, and the ESB mantra of "configuration rather than coding" is largely due to traits of the ESB service container. A service container is the physical manifestation of the abstract endpoint, and provides the implementation of the service interface. A service container is a remote process that can host software components.
A service container is simple and lightweight, but it can have many discrete functions. As shown in Figure 2, service containers take on different roles as they are deployed across an ESB.
In its simplest form, a service container is an operating system process that can be managed by the ESB's invocation and management framework. A service container provides a number of facilities for the service implementation such as event dispatch, thread management, security (encryption, authentication, and access control), and QoS via reliable message delivery. Unlike its distant cousins, the J2EE application server container and the EAI broker, the ESB service container allows the selective deployment of integration functionality exactly when and where you need it, and nothing more than what you need.
A service container can host a single service, or can combine multiple services in a single container environment (see Figure 3).
An ESB service is also scalable in a fashion that is independent of all other ESB services. A service container may manage multiple instances of a service within a container. Several containers may also be distributed across multiple machines for the purposes of scaling up to handle increased message volume (see Figure 4).
The ESB Service Interface
The ESB container provides the message flow in and out of a service. It also handles a number of facilities, such as service life cycle and itinerary management. As shown in Figure 5, the container manages an entry endpoint and an exit endpoint, which are used by the container to dispatch a message to and from the service.
Messages are received by the service from a configurable entry endpoint. Upon completion of its task, the service implementation simply places its output message in the exit endpoint to be carried to its next destination. The next destination may be a reply to the original sender of the message, or more often may be sent along to the next leg of its journey using a forwarding address. The output message may be the same message that it received. The service may modify the message before sending it to the exit endpoint. Or, in the service may create a completely new message to serve as a "response" to the incoming message and send the new message in the exit endpoint.
What is placed in the exit endpoint depends on the context of the situation and the message being processed. In the case of a content-based routing (CBR) service, the message content will be unchanged, with new forwarding addresses set in the message header.
In more sophisticated cases, one input message can transform into many outputs, each with its own routing information. For example, a splitter service can receive a purchase order document, split it into multiple output messages, and send out the purchase order and its individual line items as separate messages to an inventory or order fulfillment service. The service implementation in this case does not have to be written using traditional coding practices; it can be implemented as a specialized transformation service that applies an XSLT stylesheet to the purchase order document to produce the multiple outputs.
Process Tracking and Error Handling
In addition to a normal exit endpoint to handle the outgoing flow of a message, additional destinations are available to the service for auditing the message and for reporting errors. The tracking endpoint can be utilized to monitor the progression of a message as it travels through a business process. Tracking can be handled at both the individual service level and the business-process level. From the service implementation's point of view, it simply places data into the tracking endpoint or fault endpoint, and the surrounding ESB invocation and management framework takes care of the tracking and error reporting. This approach provides a separation between the implementation of the service and the details the surrounding fault handling. The implementer of a service need only be concerned that it has a place to put such information, whether it is information concerning the successful processing of good data, or the reporting of errors and bad data.
One of the many benefits of using itinerary-based routing to coordinate the interactions between discrete integration services is the ease with which integration patterns can be created and reused to solve common integration challenges. A message itinerary can be a powerful and flexible tool for intercepting the path of a message and performing operations on it, thus adding value to the integration environment. Through configuration and management tools, additional processing steps can be inserted into a business process definition as event-driven services into an XML processing pipeline. The following describes two of the common integration patterns in use today: the "VETO" pattern, and a variation known as the "VETRO" pattern.
The VETO Pattern
VETO is a common integration pattern that stands for Validate, Enrich, Transform, Operate (see Figure 6). The VETO pattern and its variations can ensure that consistent, validated data will be routed throughout the ESB.
The "Validate" step is usually the first part of any ESB process and can be accomplished in a number of ways. It's important that if possible, this step happen independently; this removes the burden of validation from all of the downstream service implementations and promotes reuse. Building validation directly into the first service of a process makes it difficult to insert an additional service in front of it without requiring that the new service also provide its own validation.
An example of validation is to simply verify that an incoming message contains a well-formed XML document and conforms to a particular schema or WSDL document that describes the message. This requires that the service always have available the up-to-date XML schema for a particular message type. The schema and WSDL can be kept in the directory service and managed remotely by the management infrastructure of the ESB. A service may also have scripting associated with it, which can be made available to the service as a configuration parameter
If the target data is not in XML format, or if there is no schema or WSDL available, then a custom service can be used to validate the incoming message.
The "Enrich" step involves adding additional data to a message to make it more meaningful and useful to a target service or application. The Enrich service could be implemented to invoke another service to look up additional data, or it could access a database to get what it needs.
The "Transform" step converts the message to a target format. This often involves converting the data structure to an internal canonical format, or converting from the canonical format to the target format of the "Operate" step. The target system may have its own built-in validation rules requiring that the transformation step modify the incoming data in order to prevent the target system from rejecting the message. In this sense, the transformation step is also providing pre-validation protection in a separate service that can be separately managed. While this may mean redundant logic in the short term, it provides more flexibility in the long term, because it allows the "Operate" step to focus on business logic.
The "Operate" step is the invocation of the target service or an interaction with the target application. If the target operation is an enterprise application that requires its own data format, then the previous transformation step converts the message to the target format required by the application.
Variations: The VETRO Pattern
The VETO pattern has many variations. One such variation is the VETRO pattern, which includes a "Route" step such as a content-based router service (Figure 7).
In some cases the validate, enrich, and transform steps can be accomplished in one service implementation. For example, a CBR service may use a script-based validation directly in the service itself, rather than using a separate service. This may provide some convenience, particularly if the context of validation can't easily be applied to other uses. However, keeping them as separate services further promotes loose coupling and service reuse, and allows the validation to be separately defined and managed. Through the flexibility of configuration and deployment, that choice can be revisited over time without affecting all of the application endpoints that use the pattern. The stages of the VETO pattern can be implemented as separate services that can be configured, reused, and independently swapped out for alternate implementations.
The VETO concept is profoundly simple, yet is at the heart of what an integration architect does regularly with an ESB. An ESB provides an event-driven SOA for applications in an integration fabric. Regardless of the process routing and orchestration method being used - whether itineraries or the more sophisticated process modeling using an orchestration service - it is the use of integration patterns such as VETO and its variations that provide the overall value and flexibility to the integration fabric.
I hope that this brief introduction to the ESB and its use of integration patterns has provided you with insight into the internal workings of the ESB, and given you a sense of how an integration architect can use event-driven components as services to construct reusable integration patterns in an enterprise SOA. The VETO pattern is one of many being used in ESB-based integrations.
I encourage you to learn more about the ESB as a technology concept, for it is already rapidly changing the way integration is being done across a variety of industries. So get reading, and get on the bus!
SYS-CON Events announced today that BMC Software has been named "Siver Sponsor" of SYS-CON's 18th Cloud Expo, which will take place on June 7-9, 2015 at the Javits Center in New York, New York. BMC is a global leader in innovative software solutions that help businesses transform into digital enterprises for the ultimate competitive advantage. BMC Digital Enterprise Management is a set of innovative IT solutions designed to make digital business fast, seamless, and optimized from mainframe to mo...
May. 27, 2016 01:45 AM EDT Reads: 2,079
As AT&Ts VP of Domain 2.0 architecture writes one aspect of their Domain 2.0 strategy is a goal to embrace a Microservices Application Architecture. One page 9 they describe how these envisage them fitting into the ECOMP architecture: "The initial steps of the recipes include a homing and placement task using constraints specified in the requests. ‘Homing and Placement' are micro-services involving orchestration, inventory, and controllers responsible for infrastructure, network, and applicati...
May. 27, 2016 01:30 AM EDT Reads: 1,758
SYS-CON Events announced today that EastBanc Technologies will exhibit at SYS-CON's 18th International Cloud Expo®, which will take place on June 7-9, 2016, at the Javits Center in New York City, NY. EastBanc Technologies has been working at the frontier of technology since 1999. Today, the firm provides full-lifecycle software development delivering flexible technology solutions that seamlessly integrate with existing systems – whether on premise or cloud. EastBanc Technologies partners with p...
May. 27, 2016 01:30 AM EDT Reads: 2,128
A strange thing is happening along the way to the Internet of Things, namely far too many devices to work with and manage. It has become clear that we'll need much higher efficiency user experiences that can allow us to more easily and scalably work with the thousands of devices that will soon be in each of our lives. Enter the conversational interface revolution, combining bots we can literally talk with, gesture to, and even direct with our thoughts, with embedded artificial intelligence, wh...
May. 27, 2016 01:30 AM EDT Reads: 1,948
SYS-CON Events announced today that Isomorphic Software will exhibit at SYS-CON's [email protected] at Cloud Expo New York, which will take place on June 7-9, 2016, at the Javits Center in New York City, NY. Isomorphic Software provides the SmartClient HTML5/AJAX platform, the most advanced technology for building rich, high-productivity enterprise web applications for any device. SmartClient couples the industry’s broadest, deepest UI component set with a java server framework to deliver an end-...
May. 27, 2016 01:00 AM EDT Reads: 2,047
SYS-CON Events announced today that Alert Logic, Inc., the leading provider of Security-as-a-Service solutions for the cloud, will exhibit at SYS-CON's 18th International Cloud Expo®, which will take place on June 7-9, 2016, at the Javits Center in New York City, NY. Alert Logic, Inc., provides Security-as-a-Service for on-premises, cloud, and hybrid infrastructures, delivering deep security insight and continuous protection for customers at a lower cost than traditional security solutions. Ful...
May. 27, 2016 12:45 AM EDT Reads: 2,698
SYS-CON Events announced today that Commvault, a global leader in enterprise data protection and information management, has been named “Bronze Sponsor” of SYS-CON's 18th International Cloud Expo, which will take place on June 7–9, 2016, at the Javits Center in New York City, NY, and the 19th International Cloud Expo, which will take place on November 1–3, 2016, at the Santa Clara Convention Center in Santa Clara, CA. Commvault is a leading provider of data protection and information management...
May. 27, 2016 12:00 AM EDT Reads: 3,029
Many banks and financial institutions are experimenting with containers in development environments, but when will they move into production? Containers are seen as the key to achieving the ultimate in information technology flexibility and agility. Containers work on both public and private clouds, and make it easy to build and deploy applications. The challenge for regulated industries is the cost and complexity of container security compliance. VM security compliance is already challenging, ...
May. 27, 2016 12:00 AM EDT Reads: 1,202
SYS-CON Events announced today that Tintri Inc., a leading producer of VM-aware storage (VAS) for virtualization and cloud environments, will exhibit at the 18th International CloudExpo®, which will take place on June 7-9, 2016, at the Javits Center in New York City, New York, and the 19th International Cloud Expo, which will take place on November 1–3, 2016, at the Santa Clara Convention Center in Santa Clara, CA.
May. 26, 2016 11:45 PM EDT Reads: 2,257
SYS-CON Events announced today that AppNeta, the leader in performance insight for business-critical web applications, will exhibit and present at SYS-CON's @DevOpsSummit at Cloud Expo New York, which will take place on June 7-9, 2016, at the Javits Center in New York City, NY. AppNeta is the only application performance monitoring (APM) company to provide solutions for all applications – applications you develop internally, business-critical SaaS applications you use and the networks that deli...
May. 26, 2016 10:45 PM EDT Reads: 2,358
18th Cloud Expo, taking place June 7-9, 2016, at the Javits Center in New York City, NY, will feature technical sessions from a rock star conference faculty and the leading industry players in the world. Cloud computing is now being embraced by a majority of enterprises of all sizes. Yesterday's debate about public vs. private has transformed into the reality of hybrid cloud: a recent survey shows that 74% of enterprises have a hybrid cloud strategy. Meanwhile, 94% of enterprises are using some...
May. 26, 2016 10:45 PM EDT Reads: 3,101
SoftLayer operates a global cloud infrastructure platform built for Internet scale. With a global footprint of data centers and network points of presence, SoftLayer provides infrastructure as a service to leading-edge customers ranging from Web startups to global enterprises. SoftLayer's modular architecture, full-featured API, and sophisticated automation provide unparalleled performance and control. Its flexible unified platform seamlessly spans physical and virtual devices linked via a world...
May. 26, 2016 10:15 PM EDT Reads: 2,059
While there has been much ado about interoperability, there are still no real solutions, same as last year and the year before that. The large EHR vendors who continue to dominate the market still maintain that interoperability is all but solved, still can't connect EHRs across the continuum causing frustration by providers and a disservice to patients. The ONC pays lip service to the problem, but that is about it. It is time for the healthcare industry to consider alternatives like middleware w...
May. 26, 2016 09:15 PM EDT Reads: 1,594
Join us at Cloud Expo | @ThingsExpo 2016 – June 7-9 at the Javits Center in New York City and November 1-3 at the Santa Clara Convention Center in Santa Clara, CA – and deliver your unique message in a way that is striking and unforgettable by taking advantage of SYS-CON's unmatched high-impact, result-driven event / media packages.
May. 26, 2016 08:00 PM EDT Reads: 2,323
In the rush to compete in the digital age, a successful digital transformation is essential, but many organizations are setting themselves up for failure. There’s a common misconception that the process is just about technology, but it’s not. It’s about your business. It shouldn’t be treated as an isolated IT project; it should be driven by business needs with the committed involvement of a range of stakeholders.
May. 26, 2016 08:00 PM EDT Reads: 2,366
The 19th International Cloud Expo has announced that its Call for Papers is open. Cloud Expo, to be held November 1-3, 2016, at the Santa Clara Convention Center in Santa Clara, CA, brings together Cloud Computing, Big Data, Internet of Things, DevOps, Containers, Microservices and WebRTC to one location. With cloud computing driving a higher percentage of enterprise IT budgets every year, it becomes increasingly important to plant your flag in this fast-expanding business opportunity. Submit y...
May. 26, 2016 07:00 PM EDT Reads: 1,950
Internet of @ThingsExpo, taking place November 1-3, 2016, at the Santa Clara Convention Center in Santa Clara, CA, is co-located with the 19th International Cloud Expo and will feature technical sessions from a rock star conference faculty and the leading industry players in the world and ThingsExpo New York Call for Papers is now open.
May. 26, 2016 06:00 PM EDT Reads: 1,767
IoT generates lots of temporal data. But how do you unlock its value? How do you coordinate the diverse moving parts that must come together when developing your IoT product? What are the key challenges addressed by Data as a Service? How does cloud computing underlie and connect the notions of Digital and DevOps What is the impact of the API economy? What is the business imperative for Cognitive Computing? Get all these questions and hundreds more like them answered at the 18th Cloud Expo...
May. 26, 2016 03:30 PM EDT Reads: 2,197
SYS-CON Events announced today the How to Create Angular 2 Clients for the Cloud Workshop, being held June 7, 2016, in conjunction with 18th Cloud Expo | @ThingsExpo, at the Javits Center in New York, NY. Angular 2 is a complete re-write of the popular framework AngularJS. Programming in Angular 2 is greatly simplified. Now it’s a component-based well-performing framework. The immersive one-day workshop led by Yakov Fain, a Java Champion and a co-founder of the IT consultancy Farata Systems and...
May. 26, 2016 03:30 PM EDT Reads: 3,964
SYS-CON Events announced today the Docker Meets Kubernetes – Intro into the Kubernetes World, being held June 9, 2016, in conjunction with 18th Cloud Expo | @ThingsExpo, at the Javits Center in New York, NY. Register for 'Docker Meets Kubernetes Workshop' Here! This workshop led by Sebastian Scheele, co-founder of Loodse, introduces participants to Kubernetes (container orchestration). Through a combination of instructor-led presentations, demonstrations, and hands-on labs, participants learn ...
May. 26, 2016 11:00 AM EDT Reads: 1,899