The document outlines the principles and design patterns of microservices, describing microservices as a collection of autonomous services that collectively handle specific business capabilities. It explains the importance of design patterns in ensuring consistency across development teams and provides examples such as API gateways, circuit breakers, and event sourcing. The content emphasizes the benefits of microservices, including scalability, resilience, and continuous delivery.

1. Copyright © 2017, edureka and/or its affiliates. All rights reserved.

2. www.edureka.co
PRINCIPLES BEHIND MICROSERVICES
WHAT ARE MICROSERVICES?
WHAT ARE DESIGN PATTERNS?
WHY DO WE NEED DESIGN PATTERNS?
MICROSERVICES DESIGN PATTERNS

3. WHY DO WE NEED DESIGN PATTERNS?
www.edureka.co

4. WHY DO WE NEED DESIGN PATTERNS?
www.edureka.co
Process 1 Process 2 Process 3
Works Successfully Shows few errors Shows few errors

5. WHY DO WE NEED DESIGN PATTERNS?
www.edureka.co
So, the development ream cannot build the application using the
process 2and 3

6. WHY DO WE NEED DESIGN PATTERNS?
www.edureka.co
By using Design Patterns, the team working on various
projects use the same pattern to build similar applications.

7. WHAT ARE DESIGN PATTERNS?
www.edureka.co

8. WHAT ARE DESIGN PATTERNS?
Software Design Pattern can be defined as a software
template or a description to solve a problem that occurs
in multiple instances while designing a Software
Application or a Software Framework.
DESIGNPATTERN
www.edureka.co

9. WHAT ARE MICROSERVICES?
www.edureka.co

10. WHAT ARE MICROSERVICES?
Microservices, aka Microservice Architecture, is an
architectural style that structures an application as a
collection of small autonomous services, modelled
around a business domain. In a Microservice
Architecture, each service is self-contained and
implements a single business capability.
MICROSERVICES
www.edureka.co

11. PRINCIPLES BEHIND MICROSERVICES
www.edureka.co

12. PRINCIPLES BEHIND MICROSERVICES
Independent &
Autonomous Services
DecentralizationScalability
Resilient Services
Real Time Load
Balancing
Availability
Continuous delivery
through DevOps
Integration
Seamless API
Integration &
Continuous Monitoring
Auto -Provisioning
Isolation from
Failures
www.edureka.co

13. MICROSERVICES DESIGN
PATTERNS
www.edureka.co

14. AGGREGATOR
www.edureka.co

15. AGGREGATOR
www.edureka.co
Collects Related Items Of Data And Displays Them
Based On DRY Principle
Aggregator
Service A
Service B

16. API GATEWAY
www.edureka.co

17. API GATEWAY
www.edureka.co
Can Convert The Protocol Request From One Type To Other
API Gateway Acts As An Entry Point To Forward The Clients
Requests To Appropriate Microservices
API GatewayClient Load Balancer
Service A
Service B

18. CHAINED OR CHAIN OF RESPONSIBILITY
www.edureka.co

19. CHAINED OR CHAIN OF RESPONSIBILITY
www.edureka.co
Produces A Single Output Which Is A Combination Of Multiple
Chained Outputs.
Use Synchronous HTTP Request Or Response For Messaging
Service A Service B Service C

20. ASYNCHRONUS MESSAGING
www.edureka.co

21. ASYNCHRONUS MESSAGING
www.edureka.co
All The Services Can Communicate With Each Other, But They Do
Not Have To Communicate With Each Other Sequentially
Service A Service B Service C
Queue

22. DATABASE
www.edureka.co

23. DATABASE
www.edureka.co
Database Per Service Shared Database
Service A
Service B
Service C Service D

24. EVENT SOURCING
www.edureka.co

25. EVENT SOURCING
www.edureka.co
Creates Events Regarding The Changes In The Application State
EventsPresentation Layer Event Store
Materialized View Query for Current State External Systems

26. BRANCH
www.edureka.co

27. BRANCH
www.edureka.co
Simultaneously Process The Requests And Responses From Two
Or More Independent Microservices
Service A
Service B
Service C Service D

28. COMMAND QUERY RESPONSIBILTY
SEGREAGTOR(CQRS)
www.edureka.co

29. CQRS
www.edureka.co
Application Is Divided Into Two Parts: Command And Query
Command
write
Query
read
Command Part Handles All The Requests
Related To CREATE, UPDATE, DELETE.
Query Part Takes Care Of The
Materialized Views

30. CIRCUIT BREAKER
www.edureka.co

31. CIRCUIT BREAKER
www.edureka.co
Used To Stop The Process Of Request And Response If A Service
Is Not Working.
Remote ServiceClient Load Balancer
Service A
Service C
Circuit Breaker
Service B
Down Service

32. DECOMPOSITION
www.edureka.co

33. DECOMPOSITION
www.edureka.co
Decomposition of Applications According To
Sub-Domains of
Application
Business
Capability
Strangler or Vine
Pattern

34. Copyright © 2017, edureka and/or its affiliates. All rights reserved.
www.edureka.co

35. www.edureka.co