The document discusses microservice architecture and provides advice before adopting this approach. It cautions that microservices means increased latency and failure points. Rather than rushing into microservices, it recommends first understanding how to build better monolithic systems by studying an application's behavior and true interaction patterns. The document emphasizes that loose coupling and tight cohesion are most important in application design, and advises learning from past distributed system failures before distributing a system.

1. What makes you to think that you will
succeed this time ?
μService…..
Don’t repeat SOA.

2. SOA design principles
Source : wikipedia.org
We knew this since
2005. Still we build
monolithic systems.

3. Like any other architecture…..
SOA was never about tools or technology...It's
about the principles.
Get your direction right, before deciding the
mode of transportation.

4. μService Architecture
It's not
● a Silver Bullet
● a technology or tool

5. μService Architecture
μService means latency.

6. μService Architecture
μService means more failure points.

7. Many Components + Latency
We have a long history in goofing up, while building distributed systems.
Recall COM, DCOM, CORBA, EJB and WebSERVICES (depending on whom you ask).
=
distributed system.

8. Fallacies of Distributed Computing
Most likely it will be true
even @ 2026.
-My Opinion.

9. Still there is HOPE….
Under the hood μService is
about dividing and solving.

10. Observable paradigm shift

11. ‘OS managing processes’
to
‘DataCenter/cloud OS managing applications’.
Management Plane : SHIFT 1

12. ‘portability’
to
‘Mobility’.
Management Plane : SHIFT 2

14. But, the two most important things in
application design plane are ?

15. Loose coupling
&
Tight cohesion

17. Before embarking on μService journey,
study your application behaviour closely.

18. Learn how to build a better monolithic
systems, before building μService based
systems.
At least know the true interaction pattern
within your monolithic application.

20. You don’t have to know everything. A few
really big ideas carry most of the freight.
- Charlie Munger.