Integration in easy way
Use Cases and Deployment Scope
Integration is the best word for enterprise service bus[ESB], with
ESB is possible to integrate REST, SOAP, JMS, MQTT, SQL artifact. We
used ESB to transform message in and message out. We implement a service
chain, during a service call we call more than one service and we
compose a new message as a message out. The new message contains fields from the all services response. We
also used ESB to implement message and forward, we persist message in a
JMS queue, and using message processor we analyze the message and call
more than one backend service.
Pros
- Service chain pattern
- Message transformation
- Call more than one backend service
- Call service with different protocoll as the client use
- Use file as input
- Use mail as input
Cons
- View deploy artifact in date time order
- Easy way to map data
- Easy way to manage payload
Most Important Features
- protocollo transfomation
- service configurazion and not developed
- clustering
Return on Investment
- Reduce development time to the service integration
- We can use junior developer
- Clustered in easy way
Alternatives Considered
TIBCO Enterprise Message Service and Mule ESB
Other Software Used
WSO2 API Manager, Avolution ABACUS, ReadyAPI (formerly SoapUI Pro, LoadUI Pro, & ServiceV Pro)