A move from a global Enterprise architecture to a Micro-Service architecture does not happen overnight.
When I read an interesting article on how Collateral is being transformed to a Cloud Micro-Service offering in Calypso, I could not stop smiling.
It will be interesting to understand how an exposure message will be persistent in Calypso without interacting with the famous Data-Server! How validation will happen without interacting with the Workflow?
Are we saying major functions of the Collateral module are now independent of the Calypso Data-Server architecture ? Calypso can now connect to external Data-Servers to persist data , external Market Data Servers to calculate new exposure, interest… external BO-Services to generate confirmations and transfers (important for disputes process)
And for the Optimizer no need anymore to communicate with the inventory, product definitions, haircuts, fees, market data like prices, …
It will be wonderful not to have to install most Calypso infrastructure and not to have to configure to run pieces of the Collateral module.
What I know is that it is not enough to create Web front-end screens and have a solution sits on the Cloud to say: Our solutions are now Web Micro-Services enabled! It needs deeper architectural design review.
I would love to understand how in few months an architecture like this has changed into a Micro-Service one!
Please contribute in this post to enhance our understanding.