Why Microservices
•
2 gostaram•2,892 visualizações
Presentation given during Start Up Day Hong Kong on September 15, 2017 within the Architecture track
Recomendados
Mais conteúdo relacionado
Mais procurados
Mais procurados (20)
Semelhante a Why Microservices
Semelhante a Why Microservices (20)
Mais de Amazon Web Services
Mais de Amazon Web Services (20)
Why Microservices
- 1. © 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved. Joseph Cooper, CEO @ KintoHub September 15th, 2017 AWS Startup Day Why and When You Should Adopt Microservices
- 2. Joseph Cooper • Multi-entrepreneur, 3 gaming companies, 20M+ app downloads, 6 years • Built 100+ manned companies, platforms with 250M USD transactions per year • Eats real time data problems for breakfast • Loves building infrastructure & tools specifically to make life easier for developers • Startup advisor to maximize potential • Just founded new microservice company! built US$25M biz rev per year 100+ manned companies 20M+ app downloads
- 3. Virtualization 1998 Cloud 2006 Containers 2013 147M Internet users 1,093M Internet users 2,802M Internet users 3,835M+ Internet users Source: http://www.internetworldstats.com/emarketing.htm Microservices 2018
- 4. The Monolith • Quick & Easy with humble beginnings • Simple infrastructure • Glorious debugging • Begin enjoying merge conflicts • Maxed out TCP socket connections • Deadlock and concurrency hell • Bugs galore
- 5. The Monolith • Quick & Easy with humble beginnings • Simple infrastructure • Glorious debugging • Begin enjoying merge conflicts • Maxed out TCP socket connections • Deadlock and concurrency hell • Bugs galore
- 6. EatMe.io Example • Started as simple Agar.io style game • Evolved into Card Collection Mechanics with Data-backed features • Heavy Costs @ Scale – 4M+ Downloads • 4x Nodes per region, 10x regions • 3x Databases (Live, Dev, Analytics) • Microservice Savings • Data, Auth, Real-Time decoupled • 11K USD 4K USD per month saved!
- 7. PROBLEM SOFTWARE TEAM CUSTOMER COMPLAINTS Lengthy fixes and releases Frustrated last minute changes - impatience SCALE ISSUES Hard to maintain 1M+ line code Lack of agility CRIPPLED RELEASES Takes 2 months to ship!? Who broke the build? Who owns this? Solving issues not innovating SOLUTIONS Shared libraries / code / mess Easier to break standards Hack fix prone
- 9. The Birth of Microservices
- 10. Microservices in One Line Loosely coupled service oriented architecture with bounded contexts. Adrian Cockcroft, VP of Cloud Architecture @ AWS
- 11. Microservices in One Line Loosely coupled service oriented architecture with bounded contexts.
- 12. Microservices in One Line Loosely coupled service oriented architecture with bounded contexts.
- 13. Microservices in One Line Loosely coupled service oriented architecture with bounded contexts.
- 14. Microservices to Me • A service that has the responsibility of managing one entity and/or single type of logic • Reusable code that is not bound by a specific project, but solves a specific problem
- 15. Why Microservices? • Clear responsibilities & dependencies – hard to put code in the wrong place • Small & clean packages of code • Less issues with parallel computing due to the simplicity, put scalability on infra • Opens up language agnostic possibilities • Easier to build -> dev -> test -> deploy
- 16. Microservice Principles • Build clear & clean public APIs
- 17. Microservice Principles Clear public, private and private-shared data Clients
- 18. Microservice Principles Ensure backwards compatibility publicly or externally Public Example Internal Example Version 1.1.0 Version 1.0.0
- 19. Microservice Principles • Network (TLS/VPC/Security Groups) • Containers/Servers • API Throttling • Authentication S2S and C2S • Secrets Management (vault, keywhiz) Secure Everything!
- 20. Embrace open source, it’s finally mature and waiting for you!
- 21. Embrace open source, it’s finally mature and waiting for you!
- 23. The Microservice Journey • Session Management? • Shared Data? • Forking Microservices? • Why split into 5 servers for my original monolithic app? Isn’t that 15 servers in DEV, QA and PROD?! ~ragequit~ • What is the right tool? Config, Logs, Tracing, Debugging, Discovery, Orchestration?!?!
- 24. The one-stop shop for microservices.
- 25. The Decision • Easier to manage in the long run. • Clean code, responsibilities & deps • Operationally reusable code • It’s poised to be the future. • Team size > 3 • Plan to go planet scale or experiencing growing pains • New project coming up? • Feel plateaued on product dev speed and using monolithic designs • Code agnostic hiring Why? When?