Use Case for Financial Industry using Mule ESB. This is a unique project and use case that shows, using light weight ESB like Mule it is easy to adapt and scale out on utility hardware. Besides just scale out, it is easy to migrate from a legacy batch based applications into a work flow enabled, Active-Active applications.
Overview: Me / Myself / Adhish (its all about me)
Problem Statement: Numbers (business bat) / Non Functional / Functional
Challenges: Weight Loss / Developer Debt (Sonar / SQUEL)
Before & After : Vendor Solutions Vs. Mule/Inhouse
That’s me, yehey!!!
Numbers: This project started in 2011 as a 5 year transformation.
Current Volumes: This project was started in 2012 (planning in 2011) with 5 years to go live.
Recover Time Objective: was twisted by business to Recover Time Operate.
Future business: 2015 and beyond, as this was a 5 year plan, it started back in 2011.
Storage: Played a critical aspect of the solution, we had to cut down on logging, implement other mechanism i.e. Splunk etc.
Average CPU: was based line on the older application which was in production.
Memory: same as the older application
Use of GC: …
DB Connections / MQ / Qpid etc.
Talk about the Cash Business, file based, low value, large amount of data. Compound the problem with Country / Client / Time of transmission et`c.
Talk about the complex of multiple files / clean up / data files / security / regulation(s) etc.
Mule Shipped a trainer from Antwerp (Tom) to help us get the team in Hong Kong up and running, it was a 5 days intense course with hands on lab.