Does your Microservices setup actually benefit you? Or are you bogged down with managing the network operations, observability, release management and more? A Service Mesh can actually help reduce operational complexity and manage your microservices better.

1. ©ThoughtWorks 2019

2. MONOLITH
SIMPLE TO DEVELOP EASY TO TEST
MONITORING AND
TRACING ARE
UNCOMPLICATED
STRAIGHT FORWARD
DEPLOYMENT
©ThoughtWorks 2019

3. DRAWBACKS
DEPENDENT TEAMS SCALING ISSUES
ADOPTING
NEWER
TECHNOLOGIES
Teams become dependant
on each other and the whole
system starts moving with
the speed of the slowest
team member.
Even well architected
application that has a clean
code structure, that uses
several layers of caching and
that has optimized database
structure, will eventually
reach its limit when deployed
as a monolith.
Monolithic applications
has a barrier to adopting
new technologies.
Since changes in
frameworks or languages
will affect an entire
application it is extremely
expensive in both time
and cost
TESTING &
RELEASE
MANAGEMENT
Even a small trivial bug fix
needs full round of testing.
Has very tedious release
management, it needs to co-
ordinated with all the team
and need meticulous
planning
©ThoughtWorks 2019

4. MICROSERVICE(S)
API
Gateway
DBService A
DBService B
DBService C
DBService D
©ThoughtWorks 2019

5. ADVANTAGES
INDEPENDENT
TEAMS
SCALING
NEWER
TECHNOLOGIES CAN
BE ADOPTED EASILY
Teams don’t have to
dependent on
other teams.
Scaling a particular service
service is very easy
Any new technology can
be easily adopted
TESTING &
RELEASE
MANAGEMENT
Trivial bug fix doesn’t need
full fledged test
Each and every team can
plan their release without
worrying much about the
other teams.
©ThoughtWorks 2019

6. ©ThoughtWorks 2019

7. DB
DB
Service A
Service C
©ThoughtWorks 2019

8. DB
DB
Service A
Service C
AUTHENTICATION /
AUTHORIZATION
©ThoughtWorks 2019

9. TLS
DB
DB
Service A
Service C
AUTHENTICATION /
AUTHORIZATION
TLS
©ThoughtWorks 2019

10. DB
DB
Service A
Service C
AUTHENTICATION /
AUTHORIZATION
TLS
CIRCUIT
BREAKER
©ThoughtWorks 2019

11. AUTHENTICATION /
AUTHORIZATION
TLS RATE LIMITING
CIRCUIT
BREAKER
DB
DB
Service A
Service C
©ThoughtWorks 2019

12. AUTHENTICATION /
AUTHORIZATION
TLS RATE LIMITING
RELEASE
MANAGEMENT
CIRCUIT
BREAKER
DB
DB
Service A
Service C
©ThoughtWorks 2019

13. AUTHENTICATION /
AUTHORIZATION
TLS RATE LIMITING
RELEASE
MANAGEMENT
CIRCUIT
BREAKER
MONITORING
AND ALERTING
DB
DB
Service A
Service C
©ThoughtWorks 2019

14. HOW ABOUT?
TRACING RETRY ....
MULTIPLE
PROTOCOLS
(HTTP/gRPC)
©ThoughtWorks 2019

15. DB
DB
Service A
Service C
AUTHENTICATION /
AUTHORIZATION
TLS RATE LIMITING
RELEASE
MANAGEMENT
CIRCUIT
BREAKER
MONITORING
AND ALERTING
©ThoughtWorks 2019

16. AUTHENTICATION /
AUTHORIZATION
TLS RATE LIMITING
RELEASE
MANAGEMENT
CIRCUIT
BREAKER
MONITORING
AND ALERTING
©ThoughtWorks 2019

17. AUTHENTICATION /
AUTHORIZATION
TLS
CIRCUIT BREAKER
RATE LIMITING
RELEASE MANAGEMENT
MONITORING AND
ALERTING
CUSTOM CODE VS LIBRARY?
©ThoughtWorks 2019

18. AUTHENTICATION /
AUTHORIZATION
TLS
CIRCUIT BREAKER
RATE LIMITING
RELEASE MANAGEMENT
MONITORING AND
ALERTING
HOW ABOUT IMPLEMENTING?
©ThoughtWorks 2019

19. v1.0.0
v1.0.0
v1.0.0
v1.0.0
v1.0.0
v1.0.0
v2.0.0
v2.0.0
v2.0.0
v2.0.0
v2.0.0
v2.0.0
v3.0.0
v3.0.0
v3.0.0
v3.0.0
v3.0.0
v3.0.0
v1.0.0
v1.0.0
v1.0.0
v1.0.0
v1.0.0
v1.0.0
v2.0.0
v2.0.0
v2.0.0
v2.0.0
v2.0.0
v2.0.0
v3.0.0
v3.0.0
v3.0.0
v3.0.0
v3.0.0
v3.0.0
v1.0.0
v1.0.0
v1.0.0
v1.0.0
v1.0.0
v1.0.0
v2.0.0
v2.0.0
v2.0.0
v2.0.0
v2.0.0
v2.0.0
v3.0.0
v3.0.0
v3.0.0
v3.0.0
v3.0.0
v3.0.0
v1.0.0
v1.0.0
v1.0.0
v1.0.0
v1.0.0
v1.0.0
v2.0.0
v2.0.0
v2.0.0
v2.0.0
v2.0.0
v2.0.0
v3.0.0
v3.0.0
v3.0.0
v3.0.0
v3.0.0
v3.0.0
Service E
Service F
Service G
Service H
Service A
Service B
Service C
Service D
Service I
Service J
Service K
Service L
Service M
Service N
Service O
Service P
DEPENDENCY MATRIX
©ThoughtWorks 2019

20. HOW ABOUT ROLLING OUT...
NEWER FEATURE
FIXING
SECURITY
VULNERABILITY
...
NEW
REQUIREMENTS
©ThoughtWorks 2019

21. https://www.sciencemag.org/news/2015/07/why-screams-are-so-scary
Photo by Tim Gouw on Unsplash
©ThoughtWorks 2019

22. What's the solution?
©ThoughtWorks 2019

23. Out Of
Process
Out Of Process
Out Of Process
OUT OF PROCESS
NEWER FEATURE
DB
DB
Service A
Service C
©ThoughtWorks 2019

24. Out Of Process
AUTHENTICATION /
AUTHORIZATION
TLS
CIRCUIT BREAKER
RATE LIMITING
RELEASE MANAGEMENT
MONITORING AND
ALERTING
PROXY
©ThoughtWorks 2019

25. API
Gateway
DB
DB
DB
DB
PROXY
PROXY
PROXY
PROXY
Service A
Service C
Service D
Service B
©ThoughtWorks 2019

26. API
Gateway
DB
DB
DB
DB
PROXY
PROXY
PROXY
PROXY
Service A
Service C
Service D
Service B
SERVICE MESH
©ThoughtWorks 2019

27. SERVICEMESH DEPLOYMENT - SIDECAR
©ThoughtWorks 2019

28. SERVICEMESH ARCHITECTURE
©ThoughtWorks 2019

29. Demo
©ThoughtWorks 2019

30. Do you need a Service Mesh?
©ThoughtWorks 2019

31. TOOLS IN THE MARKET
Linkerd
Consul
Connect
©ThoughtWorks 2019

32. FUTURE OF SERVICE MESH
App
Mesh
©ThoughtWorks 2019

33. SERVICE MESH
©ThoughtWorks 2019

34. #TWISummit
Please share your feedback with
arvindt@thoughtworks.com
subramk@thoughtworks.com
THANK YOU!
©ThoughtWorks 2019