Brief description: This ppt attempts to give an overview of microservices. It covers many topics but especially focuses on the design patterns of microservices. This ppt covers everything from history of how microservices came to be, to the different ways they communicate with each other, and their various design patterns and finally how the microservices can be deployed. Long description: The ppt begins with why the need was felt to shift from monolithic architecture, to how it evolved to SOA and finally microservice architecture. It explains what microservices are, and the different ways ( synchronous and asynchronous ) the microservices communicate with each other. It also briefly talks about REST APIs. Further, it delves into all the microservice patterns: Config server, naming server, Circuit breaker, API Gateway, and distributed tracing. Finally, it attempts to explain how to deploy microservices using Docker and Kubernetes

2. CONTENTS
• Microservice VS Monolithic
• Challenged with Monolithic Architecture
• What is a microservice
• Core Components of Microservice
• Rest API
• Components
• Naming Server
• Spring Cloud Config Server
• Circuit Breaker
• API Gateway
• Routing and Messaging
• Distributed Tracing
• Docker
• Kubernetes
• Demo
• Q and A session

4. MONOLITH

6. SOA

7. WHAT IS A MICROSERVICE

9. COMMUNICATION BETWEEN
MICROSERVICES

10. REST API

12. • We use Config server to manage external properties with
config server for applications across all environments

13. ARCHITECTURE

14. • Also known as Service Discovery
• Two discovery patterns:
• Client-side discovery and Server-side discovery

15. ARCHITECTURE

16. • Acts as a fault – tolerance robust system
• The circuit breakers have three states:
Open
Closed
Half-open State.
•
Circuit Breaker

17. ARCHITECTURE

18. • Unified interface to a client
• Performs dynamic routing of microservice applications

19. ARCHITECTURE

20. • Inter Process Communication Library is used
• Communication using HTTP is supported
Routing and Messaging

21. ARCHITECTURE

22. • Helps gather timing data
• Provides a mechanism for sending, receiving and visualising
traces
Distributed Tracing

23. • Encapsulates the microservice into a Docker Container
• Containers include all resources the software would need
DOCKER

24. • Open-source container orchestration platform for managing,
automating, and scaling containerized applications
KUBERNETES

25. https://medium.com/@shrutiebony/all-about-microservices-in-350-words-
ee2f27287a6?source=friends_link&sk=50883306a90d6301c9ff8e8a57d19d48
Link - My Blog ( All about microservices in 350
words)

26. By
Shruti and Praful