Microservices Architectures

Brief overview of what microservices architectures are, including benefits and challenges.

Transcript

1. Microservices Architectures Hooklift, Inc. Camilo Aguilar - Founder at Hooklift, Inc. @c4milo at Twitter and Github
2. – Adrian Cockcroft, Netflix, Inc. “It is a service-oriented architecture composed of loosely coupled elements that have bounded contexts.” What is it? Hooklift, Inc.
3. Hooklift, Inc. Image Source: http://martinfowler.com/bliki/BoundedContext.html What is it?
4. Monolithic Image source: http://www.infoq.com/presentations/migration-cloud-microservices Hooklift, Inc.
5. Hooklift, Inc. Image source: http://www.infoq.com/presentations/migration-cloud-microservices Microservices
6. Hooklift, Inc. Microservices benefits business and developers
7. Deployments per day • Flickr: 10 • Etsy: 50 • Netflix: 100 • HubSpot: 300 • Twitter: 7200 • Amazon: 7800 Hooklift, Inc. Reasoning: The smaller the change the lower the risk Also: Continuous delivery of business value
8. However, there are also new challenges Hooklift, Inc.
9. Hooklift, Inc. Wheel of Doom
10. Hooklift, Inc. Image source: http://www.infoq.com/presentations/migration-cloud-microservices
11. Hooklift, Inc.
12. If you don’t have a plan you will choke yourself out Hooklift, Inc.
13. How do we get there? Hooklift, Inc.
14. Ideally, organically Hooklift, Inc.
15. Do not force it Hooklift, Inc.
16. Start with well architected monolithic Hooklift, Inc. The Clean Architecture: https://8thlight.com/blog/uncle-bob/2012/08/13/the-clean-architecture.html
17. Hooklift, Inc. Image source: http://www.codeproject.com/Articles/1064240/Introduction-to-Software-Architecture Start with well architected monolithic
18. Know when to split out Hooklift, Inc. 1. User traffic is higher compared to other parts of the app. 2. A specific context changes too often due to business requirements. 3. A different team or developer is in charge of a the specific feature. 4. There might be more patterns that I’m overlooking right now.
19. Hooklift, Inc. Have a plan 1. Deployment 2. Configuration 3. Secrets 4. Scaling 5. Metrics and Monitoring 6. Testing 7. Log management 8. Service Discovery DevOps
20. Foster a DevOps culture Hooklift, Inc.
21. Cultural change in practices and communication to quickly deliver business value Hooklift, Inc. DevOps
22. Hooklift, Inc. 1. Is not Docker 2. Is not Terraform 3. Is not Kubernetes 4. Is not Mesos 5. Is not a team or role DevOps
23. Hooklift, Inc. DevOps 1. No more tickets for IT to provision virtual machines 2. No more tickets for IT at all 3. Developers own the application and its virtual infrastructure 4. IT trusts and verifies 5. IT joins product teams and stops being in isolation
24. DevOps is a cultural change Hooklift, Inc.
25. You must have a DevOps culture first Hooklift, Inc.
26. Microservices are not going to fix a broken culture Hooklift, Inc.
27. Thanks! Hooklift, Inc. Camilo Aguilar - Founder at Hooklift, Inc. @c4milo at Twitter and Github