Think Small To Go Big - Introduction To Microservices
Download as PPTX, PDF14 likes3,757 views
The document provides an introduction to microservices architecture. It discusses how monolithic applications struggle with the need for speed, scale, and flexibility in modern cloud environments. Microservices address these challenges by decomposing applications into smaller, independent services. Each service runs in its own process and communicates over lightweight protocols like HTTP. This allows services to be developed, deployed, and scaled independently. The document outlines guidelines for designing microservices as well as benefits like improved understandability, reliability, and technology choice. It also notes potential downsides around complexity and testing. Examples are provided to illustrate differences between monolithic and microservice architectures.
Think Small To Go Big - Introduction To Microservices
- 1. Think Small To Go Big â An Introduction To Microservices By: Ryan Baxter @ryanjbaxter http://ryanjbaxter.com 3/11/15
- 2. We Have A Need For Speed 1
- 4. âŠ.but we couldnât deploy fast enough 3
- 5. Now We Have DevOps 4
- 6. âŠ.but getting infrastructure takes too long 5
- 7. The Cloud Made Infrastructure Easy 6
- 8. âŠbut our apps were not built for the cloud 7
- 9. Infrastructure That Is Out Of Our Control 9
- 11. How Did We Solve This Problem Before? 11
- 12. Scaling Horizontally Is Cheaper 12
- 13. We End Up With Something Like This 13 Load Balancer
- 15. Requires A New Way Of Thinking ï§ Our old application designs just canât keep up ï§ Massive monolithic applications break down under these new challenges 15
- 16. We Need A New Architecture ï§ Applications that are composed of smaller more focused âmicroâ apps 16
- 17. What is a Microservice? âIn short, the microservice architectural style is an approach to developing a single application as a suite of small services, each running in its own process and communicating with lightweight mechanisms, often an HTTP resource API.â - Martin Fowler 17
- 18. Itâs Not All About The Code 18
- 19. Guidelines For Microservices ï§ Make each one focused â no real rule on size ï§ â2 pizza teamsâ ï§ Each service should be treated like one app ï§ Have its one SCM repo, own pipeline, etc ï§ Should not require the use of other services ï§ Service owners are responsible for the entire lifecycle ï§ Use lightweight protocols ï§ Use the right tool for the job 19
- 20. Guidelines For Microservices ï§ Each service should have its own datastore ï§ Failure will happen, design for it ï§ Automate everything 20
- 21. Isnât This Just SOA? ï§ Hot topic, they are certainly very similar and try to solve the same problem ï§ SOA was always considered very heavy ï§ ESBs ï§ Driven by vendors ï§ SOA allowed for monoliths ï§ SOA was more about reuse than team organization and application architecture 21
- 22. Benefits Of Microservices ï§ Code for each service is easier to understand ï§ Small code base means more speed ï§ Each service can be deployed independently ï§ Failures do not bring down the whole app ï§ Technology flexibility ï§ Easier to evolve ï§ Well defined APIs 22
- 23. Cons Of Microservices ï§ Complexity ï§ You have to manage multiple apps ï§ Deploying 1 feature may involve coordination between multiple services ï§ Performance â multiple service calls ï§ When to switch to microservices ï§ Dev tools focus on monolithic apps ï§ Duplication of code ï§ End To End Testing 23
- 24. DEMO 24
- 26. Failures In A Monolith 26 Client Side Code App Sessions APIs Questions APIs Twilio Endpoint DB SMS/Email Service
- 27. Scaled Monolith 27 My App 1 DB Client Side Code App Sessions API Twilio Endpoint Questions API Load Balancer My App 1 SMS/Email Service Client Side Code App Sessions API Twilio Endpoint Questions API SMS/Email Service
- 28. Microservices Architecture 28 Client Side Code Sessions Service Questions Service Reply Service Twilio Service SendGrid Service Sessions DB Questions DB Message Queue
- 29. Client Fragility 29 Client Side Code Sessions Service Questions Service Reply Service Twilio Service SendGrid Service Sessions DB Questions DB Message Queue
- 30. API Gateways 30 Sessions Service Questions Service Reply Service Twilio Service SendGrid Service Sessions DB Questions DB Message Queue API GatewayClient Side Code
- 31. Scaling A Service 31 Sessions Service Questions Service Reply Service Twilio Service SendGrid Service Sessions DB Questions DB Message Queue Sessions Service API GatewayClient Side Code
- 32. Service Discovery 33 Sessions Service Questions Service Reply Service Twilio Service SendGrid Service Sessions DBQuestions DB Message Queue Sessions Service API GatewayClient Side Code Service Discover y
- 33. Service Discovery ï§ Eureka â Neflix OSS Component ï§ Zookeeper â Apache Project ï§ Consul 34
- 35. DEMO 36
- 36. Containers/Docker ï§ Is a great deployment and isolation tool for your microservices ï§ Allows your microservices to run on various clouds ï§ Need to use some kind of container management tool to orchestrate, monitor, and scale your microservices 37
- 37. Platform-as-a-Service ï§ Deploying a large scale distributed set of apps requires a lot of effort (even if you are using Docker) ï§ A platform-as-a-service can make it somewhat easier ï§ Built in monitoring, recovery, and scaling can really go a long way ï§ Deployments are also much easier because you just provide the code ï§ Take a look at any Cloud Foundry based PaaS 38
- 38. Deploying Microservices With Cloud Foundry ï§ Easy as cf push appname âp <jar file> ï§ Or use Cloud Foundry Maven or Gradle plugin ï§ You can use blue/green deployments to make sure you have no downtime during deploys ï§ Each microservice can be used as a Cloud Foundry service to facilitate service discovery ï§ Built-in load balancer can help with dynamic scaling ï§ Everything can be automated so it all happens on commit 39
- 39. Netflix ï§ The poster child for microservices ï§ They have a great set of open source libraries in the Neflix OSS project ï§ Service Discovery, Circuit Breakers, Service To Service Communication, and much much moreâŠ ï§ Check out Spring Cloud if you are a Spring user, very easy to integrate Netflix OSS into your apps 40
- 41. Thank you.