1. Migrate2Micro-services
A real case study

2. Why do we write software ?
Instead, let us ask: Why not to write software? What is the other alternative today which sustainably reduces lead time to do business impact* ?
If machines start writing the business logic faster and more accurately than humans beings, then we would very well use that alternative, if it exists.
Software and its associate hardware is a ‘cost’ not an asset. *Source: Dan North’s talk

3. Analogy: On-premise Monoliths vs Micro-services on Cloud
You want to travel from Point A to Point B : This is the business impact you want.
Option 1 monolithic car Buy a car. Learn to drive it. Maintain it and pay for its fuel.
Option 2microservice car Pay for ‘travel-as-a-service’ provider like Uber.* * Studies show that, at current rates, you shall pay an order lower to Uber for the next 10 years compared to the TCO (total cost of ownership) per km of a car over its lifetime. Why? Because, your car stays idle in the parking lot while in the case of Uber, the same car is driven all day.

4. Case Study
– earliest implementations were PLSQL driven, i.e. business logic was embedded in the SQL views and EJB
application

5. Total Cost of Ownership (TCO)-application SDLC

6. Total Cost of Ownership – Infrastructure

7. Why lower TCOs with micro-services based architectural style
By its very nature, rapid application deployment, rapid provisioning, network monitoring is a pre-requisite
Coupled with consistent environments with help of Docker allows lower foot-print
Cloud gives PaaS alongwith IaaS
A 2 pizza team are better manageable than 20+ teams for the same project
Divide-and-conquer strategy applied to business domain complexity. Micro-services keeps it simple and sweet in the longer term
Thus, your developers’ focus is on the business logic not deployment or server infrastructure maintenance
Polyglot, when needed in the future.

8. Things to be aware
Despite ‘you maintain what you developed’ approach as advised, core developers will move to other development projects
Application logs indexing, searching, tracing and proper monitoring tools is a necessity
New kind of bugs to deal with:
duplicate rows in dB (multi-pod apps processing same messages)
Transaction spread across different micro-services. Partial rollback.
Idempotency bugs

9. Queries ?
Thank you -- Sandesh Gandhi ( )