The document summarizes the evolution of software development at NashTech from monolithic applications to microservices and cloud native applications. It describes how NashTech moved from monoliths to bounded contexts with event-driven architecture to containerization and cloud native practices. It then discusses how developers work with microservices using client-server models, facades, proxies, circuit breakers and distributed state. Finally, it introduces service meshes as a way to provide resiliency, traffic control, security and observability across microservices through the use of proxies, sidecars and an orchestration layer like Istio.

1. Microservices to Service Mesh
@thangchung + @thinhnotes
July 2018

2. Important Notes
• Key Takeaways
- Evolution of Software Development in NashTech
- Software Developer Craftsmanship
- Cloud Native
- Service Mesh
- Myth from Modern Era
• What is NOT?
- Asynchronous Communication
- Eventually Consistency Mechanism for Data
- Stateful Service or Application
- Testing Strategy in distributed system
• Q&A

3. Evolution of Software Development in NashTech
Let’s begin with what NashTech’ Solution Architects do so far…

4. Requirements

5. NashTech Story
~  2015
Monolith Application
Monolith Application - Modular
Bounded Context
Event Driven Architecture

6. NashTech Story
2016 
Early 2017
Legacy
Systems &
COTS
• Bounded Context
• Event Driven Architecture
• Strangling Pattern
• Containerization
• 12 factors App Principles
• Infrastructure as Code 2017  ~
Cloud Native

7. NashTech Story
Reference at Steinzeit war gestern! Die vielfältigen Wege der Cloud-nativen Evolution

8. Software Developer Craftsmanship
Let see how NashTech developers do on the daily basis…

9. Developer Story
Business Code

10. Developer Story
Business Code
Client – Server
Model

11. Developer Story
Business Code
Facade / Proxy
(RPC)

12. Developer Story
Business Code
Facade / Proxy
(RPC)
WAITING

13. Developer Story
Business Code
Facade / Proxy
(RPC)
WAITING

14. Developer Story
Business Code
Facade / Proxy
(RPC)

15. Developer Story
Business Code
Facade / Proxy
(RPC)
Circuit Breakers
/ Timeouts
Telemetry

16. Developer Story
Business Code
Facade / Proxy
(RPC)
Circuit Breakers
/ Timeouts
Telemetry

17. Developer Story
Business Code
Facade / Proxy
(RPC)
Circuit Breakers
/ Timeouts
Telemetry
WAITING WAITING
WAITING

18. Developer Story
Business Code
Facade / Proxy
(RPC)
Circuit Breakers
/ Timeouts
Telemetry
WAITING WAITING
WAITING
WAITING
WAITING WAITING
WAITING

19. Developer Story
Business Code
Facade / Proxy
(RPC)
Circuit Breakers
/ Timeouts
Telemetry
Business Code
Facade / Proxy
(RPC)
Circuit Breakers
/ Timeouts
Telemetry
Business Code
Facade / Proxy
(RPC)
Circuit Breakers
/ Timeouts
Telemetry

20. Developer Story
Business Code
Facade / Proxy
(RPC)
Circuit Breakers
/ Timeouts
Telemetry
Business Code
Facade / Proxy
(RPC)
Circuit Breakers
/ Timeouts
Telemetry
Business Code
Facade / Proxy
(RPC)
Circuit Breakers
/ Timeouts
Telemetry
State???

21. Developer Story
Business Code
Facade / Proxy
(RPC)
Circuit Breakers
/ Timeouts
Telemetry
Business Code
Facade / Proxy
(RPC)
Circuit Breakers
/ Timeouts
Telemetry
Business Code
Facade / Proxy
(RPC)
Circuit Breakers
/ Timeouts
Telemetry
Distributed State Distributed State Distributed State
All Circuit
Breakers share
State

22. Developer Story
Business Code
Facade / Proxy
(RPC)
Circuit Breakers
/ Timeouts
Telemetry
Business Code
Facade / Proxy
(RPC)
Circuit Breakers
/ Timeouts
Telemetry
Business Code
Facade / Proxy
(RPC)
Circuit Breakers
/ Timeouts
Telemetry
Distributed State Distributed State Distributed State
Which one is
HEALTHY?

23. Developer Story
Business Code
Facade / Proxy
(RPC)
Circuit Breakers
/ Timeouts
Telemetry
Business Code
Facade / Proxy
(RPC)
Circuit Breakers
/ Timeouts
Telemetry
Business Code
Facade / Proxy
(RPC)
Circuit Breakers
/ Timeouts
Telemetry
Distributed State Distributed State Distributed State
DNS looks like
Client-side Service
Discovery
Client-side Service
Discovery
Client-side Service
Discovery

24. WTFun for Application Modernization?
Just for RPC Reliability &
Resiliency
Then, 5 Cloud
Commandments
Then, 8 Fallacies of
Distributed Computing
Then, 12 Factor App
Principals
Loose Polyglot, Hard
to Change……

25. Cloud Native
Everywhere is cloudy, especially in NashTech…

26. Cloud Native Application Maturity

27. Cloud Native Application Development
Reference from Cloud Native Application development - A New Computing Paradigm by Oracle
2017

28. What make different?
2017

29. DEMO: Build Microservices Application on Kubernetes

30. DEMO: Lift and Shift the Application
Development Build Shift
Dockerfile
Docker Hub

31. Service Mesh
Let’s mess everything up, but tidy it right later on…

32. Development View
Business Code
Facade / Proxy
(RPC)
Circuit Breakers
/ Timeouts
Telemetry
Distributed State
Client-side Service
Discovery
Business Code
Facade / Proxy
(RPC)
Circuit Breakers
/ Timeouts
Telemetry
Distributed State
Client-side Service
Discovery

33. Development View
Business Code
Facade / Proxy
(RPC)
Circuit Breakers
/ Timeouts
Telemetry
Distributed State
Client-side Service
Discovery
Business Code SDK

34. Development View
Business Code SDK
SCARY WORLD

35. Development View
Business Code SDK
SCARY WORLD

36. Development View
Business Code SIDECAR
SCARY WORLD

37. Development View
Business Code SIDECAR
SCARY WORLD

38. Development View
SCARY WORLD

39. Orchestrator View
Business Code
Facade / Proxy
(RPC)
Circuit Breakers
/ Timeouts
Telemetry
Distributed State
Client-side Service
Discovery
SERVICE
PLATFORM
Sidecar
SCARY WORLD

40. Orchestrator View
Business Code
Resiliency
SERVICE
PLATFORM
Sidecar
SCARY WORLD

41. Orchestrator View
Resiliency
PLATFORM
Traffic
Control
Security Availability
Business Code
SERVICE
Sidecar
SCARY WORLD

42. Mesh it up
SERVICE MESH
PLATFORM
Business Code
SERVICE
Sidecar

43. Mesh it up
SERVICE MESH
PLATFORM
Business Code
SERVICE
Sidecar
CONTROL
PLANE
DATA
PLANE

44. Service Mesh Umbrella
NELSON
CONTROL PLANE DATA PLANE
You name it…

45. Business Code
SERVICE
Proxy Architecture
Sidecar
https://www.slideshare.net/datawire/lyfts-envoy-from-monolith-to-service-mesh-matt-klein-lyft/12
• Edge Proxy
• Shared Proxy
• Sidecar Proxy

46. Istio Architecture

47. Istio Architecture: Traffic Control
Reference at http://blog.christianposta.com/microservices/low-risk-monolith-to-microservice-evolution-part-ii
Egress

48. Istio Architecture: Resiliency
• Load Balancing
• Timeout
• Retry
• Circuit Breaker
• Pool Ejection

49. Istio Architecture: Chaos Testing
• HTTP Errors
• Delays

50. Istio Architecture: Observability
Observability
Metrics
LogsTraces

51. Istio Architecture: Security
• Blacklist

52. Istio Architecture: Security
• Whitelist

53. DEMO: BookInfo

54. WTFun for Application Modernization?
Just for RPC reliability
Then, 5 Cloud
Commandments
Then, 8 Fallacies of
Distributed Computing
Then, 12 Factor App
Principals
……

55. Myth from Modern Era
Greek is a modernized life in the ancient world, but we can make it even
better nowadays...

56. The Myth
Images source at https://printablefreecoloring.com

57. The Myth
Images source at https://printablefreecoloring.com

58. The Myth
Images source at https://printablefreecoloring.com

59. The Myth
Images source at https://printablefreecoloring.com

60. The Myth
Images source at https://printablefreecoloring.com
…

61. The Myth
Images source at https://printablefreecoloring.com
…

62. THANK YOU
www.nashtechglobal.com

63. Q&A