Se ha denunciado esta presentación.
Se está descargando tu SlideShare. ×

Microservice at a glance

Anuncio
Anuncio
Anuncio
Anuncio
Anuncio
Anuncio
Anuncio
Anuncio
Anuncio
Anuncio
Anuncio
Anuncio
Próximo SlideShare
Microservice intro
Microservice intro
Cargando en…3
×

Eche un vistazo a continuación

1 de 18 Anuncio

Más Contenido Relacionado

Presentaciones para usted (20)

Similares a Microservice at a glance (20)

Anuncio

Más reciente (20)

Microservice at a glance

  1. 1. Resutain - Journey from Monolith to Microservices @ketanghumatkar
  2. 2. Microservices at a glance @ketanghumatkar
  3. 3. Monolith Presentation logic Business logic Database access logic Application integration logic
  4. 4. Downside of Monolithic Application Overloaded IDE Overloaded web container - big startup time - developer impact Continuous deployment is difficult - even small change needs entire deployment Scaling the application can be difficult Obstacle to scaling development Requires a long-term commitment to a technology stack
  5. 5. What is Microservices - Architectural pattern - Isolated services interacts with each other - May/May not have their independent db - Loosely coupled, collaborating services
  6. 6. Why Microservices are in boom Three Reasons 1. Startup boom at late 2000 2. Cloud services 3. Comfort with distributed system
  7. 7. When to do microservices 1. One part of application has higher load than other part of application 2. Different product engineering teams 3. Better code management 4. Use best technology stack to solve specific problem
  8. 8. Example Online shopping Online food delivery Online Laundry
  9. 9. Online Shopping ● Basic information about the book such as title, author, price, etc. ● Your purchase history for the book ● Availability ● Buying options ● Other items that are frequently bought with this book ● Other items bought by customers who bought this book ● Customer reviews ● Sellers ranking ● Product Info Service - basic information about the product such as title, author ● Pricing Service - product price ● Order service - purchase history for product ● Inventory service - product availability ● Review service - customer reviews …
  10. 10. Two Approaches to decompose 1. By Business Capabilities
  11. 11. Two Approaches to decompose 2. By Subdomain ● Core - key differentiator for the business and the most valuable part of the application ● Supporting - related to what the business does but not a differentiator. These can be implemented in-house or outsourced. ● Generic - not specific to the business and are ideally implemented using off the shelf software
  12. 12. Deployment Patterns ● Multiple service instances per host((Physical or Virtual machine) ● Service instance per host ● Service instance per VM(EC2 AMI, Azure VM) ● Service instance per Container(Amzon EC2 Container Service) ● Serverless deployment(AWS Lamda, Azure function) ● Service deployment platform(Kubernetes, Docker storm)
  13. 13. Communication Style 1. Remote Procedure Invocation - request/reply based protocol a. REST b. gRPC c. Apache Thrift 2. Messaging - asynchronous communication a. Apache Kafka b. RabbitMQ 3. Domain Specific Protocol a. Email protocols such as SMTP and IMAP b. Media streaming protocols such as RTMP, HLS, and HDS
  14. 14. API GATEWAY PATTERN
  15. 15. API GATEWAY PATTERN
  16. 16. Additional Points 1. Database Management a. Database as service b. Shared Database c. API Composition 2. Testing a. Service Component Test b. Service Integration Contract Test 3. Observability a. Log aggregation b. Application Metrics c. Audit Logging
  17. 17. Exercise
  18. 18. Thank You!

Notas del editor

  • Amazon, Netflex, Ebay initially all were monolith
  • Continuous delivery Continuous deployment
  • API GATEWAY MICROSERVICES
    SINGLE SERVICE AS CONTAINER
  • Example - NETFLEX

×