Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

Is orchestration an ESB responsibility?

Is an Enterprise Service Bus (a tool that acts as a mediator, a message broker, a service enabler, schema transformation enhancer, transparent location provider, service aggregator, load balancer, monitor, and all that stuff) responsible to orchestrate services?

What about putting an automated business business process with more than thousand steps and dozens of service invocations inside your enterprise service bus?

Would you do it, or would you use a specialist in orchestration such as a BPEL engine?

Please gimme you opinion.

like image 714
paulosuzart Avatar asked Dec 06 '08 02:12

paulosuzart


People also ask

What is ESB orchestration?

Orchestration can be seen as combining service calls to create higher-level, more useful composite services, but also often has a definitive "business-level" ring, and in this case is shorthand for implementing business-level processes combining business-specific services across applications and information systems.

What is the role of ESB?

An enterprise service bus (ESB) is a software platform used to distribute work among connected components of an application. It is designed to provide a uniform means of moving work, offering applications the ability to connect to the ESB and subscribe to messages based on simple structural and business policy rules.

What is ESB example?

ESB allows you to isolate the client and make some basic changes to the message. For example, changing date format of incoming message or appending informational data to messages. ESB lets you transform an incoming message into several outgoing formats and structure. For example, XML to JSON, XML to Java objects.

What is ESB in Java?

An enterprise service bus (ESB) implements a communication system between mutually interacting software applications in a service-oriented architecture (SOA).


1 Answers

Yes and no. There's a thin, and sometimes indistinguishable line between orchestration and aggregation/service augmentation.

In general, if you've got any long-running or complex business process (process being the key word, although I'm going to avoid defining it) - that's best suited to BPEL.

Simple tasks, such as aggregating the results of three service calls, could and often should be done in an ESB layer.

It's not worth losing too much sleep over, though

Disclaimer: I am an IBM ESB consultant, although I'm not writing this in an official capacity.

like image 54
Andrew Ferrier Avatar answered Sep 20 '22 17:09

Andrew Ferrier