Editing Enterprise service bus (section)

==Architecture==
The concept of the enterprise service bus is analogous to the [[Bus (computing)|bus]] concept found in [[Computer architecture|computer hardware architecture]] combined with the modular and concurrent design of high-performance computer operating systems. The motivation for the development of the architecture was to find a standard, structured, and general purpose concept for describing implementation of [[Loose coupling|loosely coupled]] software components (called [[Service (systems architecture)|services]]) that are expected to be independently deployed, running, heterogeneous, and disparate within a network. ESB is also a common implementation pattern for [[service-oriented architecture]], including the intrinsically adopted network design of the [[World Wide Web]].

No global standards exist for enterprise service bus concepts or implementations.<ref>{{cite web
 |first=Raul
 |last=Lapeira
 |title=ESB is an architectural style, a software product, or a group of software products?
 |url=http://www.consultoriajava.com/articulos/esb_arquitecture_software_product.jsp
 |publisher=Artifact Consulting
 |access-date=2010-04-16
 |quote=The first thing an ESB architect should have in mind is that as of 2010 there is no global standard for ESB.
 |archive-url=https://web.archive.org/web/20140808053149/http://www.consultoriajava.com/articulos/esb_arquitecture_software_product.jsp
 |archive-date=2014-08-08
 |url-status=dead
}}</ref> Most providers of [[message-oriented middleware]] have adopted the enterprise service bus concept as ''de facto'' standard for a service-oriented architecture. The implementations of ESB use [[event-driven architecture|event-driven]] and standards-based message-oriented middleware in combination with [[message queue]]s as technology frameworks.<ref>Curry, Edward. 2004. [http://www.mendeley.com/download/public/1652511/4338215212/cce0f06f047faa57879a1fc36a8e8d6d754d2f6a/dl.pdf "Message-Oriented Middleware"]{{dead link|date=September 2017 |bot=InternetArchiveBot |fix-attempted=yes }}. In ''Middleware for Communications'', ed. Qusay H. Mahmoud, 1-28. Chichester, England: John Wiley and Sons. {{doi|10.1002/0470862084.ch1}}. {{ISBN|978-0-470-86206-3}}</ref> However, some software manufacturers relabel existing middleware and communication solutions as ESB without adopting the crucial aspect of a bus concept.

===Functions===
An ESB applies the design concept of modern [[operating system]]s to independent services running within networks of disparate and independent computers. Like concurrent operating systems, an ESB provides commodity services in addition to adoption, translation and routing of client requests to appropriate answering services.

The primary duties of an ESB are:
* Route messages between services
* Monitor and control routing of message exchange between services
* Resolve contention between communicating service components
* Control deployment and versioning of services
* Marshal use of redundant services
* Provide commodity services like event handling, data transformation and mapping, message and event queuing and sequencing, security or [[exception handling]], protocol conversion and enforcing proper quality of communication service.