Fun Times With Microservices
Download as PPTX, PDF•1 like•963 views
Microservices are defined as a suite of small, independent services interacting through lightweight protocols, focused on specific business capabilities, and capable of independent deployment. The approach promotes scalability, agility, and reduced risk for innovation compared to traditional monolithic architectures. While microservices offer significant benefits, they also present challenges that require careful management and simplification during initial implementation.
Fun Times With Microservices
- 1. MicroServices By Christo Crampton, Tangent Solutions @toast38coza
- 3. –Adrian Cockroft “Loosely coupled service oriented architecture with bounded contexts.”
- 4. –Adrian Cockroft ‘ "fine grained SOA." In a microservices architecture, an application is comprised of a number of small, independent composable services that interact by way of an external published protocol, such as REST, or a messaging service. Each service is focused on an individual targeted business capability, and thus its scope is minimized. For functionality out of scope, the microservice calls out to other microservices via the published protocol. Each microservice should not depend on other microservices: It can be deployed, scaled, and managed independently with no effect on other microservices.’
- 5. “..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. These services are built around business capabilities and independently deployable by fully automated deployment machinery.” - Martin Fowler
- 6. Microservices • Are a suite of small, lightweight services • Which, Interact over lightweight protocol • Built, around business capability • Independently deployed, scaled and managed
- 8. So what’s wrong with the monolith? Eugene Dvorkin http://eugenedvorkin.com/seven-micro-services-architecture-advantages/
- 11. Benefits
- 12. Small easy to understand codebase
- 13. Easy to deploy
- 14. Easy to scale
- 16. Stay agile at Scale
- 17. Get Started • Build your next business capability as a small service (or extract a capability into a small service) • Make it awesome • Re-use your experience • Get better with each iteration • Profit
- 18. Fork us • https://github.com/TangentMicroServices • http://eepurl.com/98-Cj
- 19. Resources - Reading List • http://martinfowler.com/articles/microservices.html • http://www.slideshare.net/adrianco/architectures-for-high-availability-qconsf • http://www.activestate.com/blog/2014/08/microservices-and-paas-part-i • http://www.activestate.com/blog/2014/08/microservices-and-paas-part-ii • http://www.activestate.com/blog/2014/08/microservices-and-paas-part-iii • http://www.activestate.com/blog/2014/08/microservices-and-paas-part-iv • http://jimplush.com/talk/2015/02/28/microservices-allow-for-localized-tech-debt/ • http://www.slideshare.net/parikhk/restli-and-deco • http://www.slideshare.net/adriancockcroft/dockercon-state-of-the-art-in-microservices • https://engineering.groupon.com/2013/misc/i-tier-dismantling-the-monoliths/ • http://www.infoq.com/news/2014/06/soundcloud-microservices • http://eugenedvorkin.com/seven-micro-services-architecture-advantages/ • http://www.slideshare.net/LappleApple/gilt-from-monolith-ruby-app-to-micro-service-scala-service-architecture?related=1
- 20. Questions?
- 21. c. Hafnarfjorour
- 22. The following slides weren’t in the presentation, but might still be interesting …
- 23. Resources - People and Organizations • Martin Fowler and Thoughtworks • Adrian Cockraft and Netflix
- 24. “MicroServices move the complexity from the code to the infrastructure.” Build competencies
- 25. Why micro services? • Scalability, agility and speed • Smaller batches • Localize Technical Debt. • Iterative • The technology is here
- 26. It’s not all unicorns and roses What makes MicroServices good is also what makes them difficult.
- 27. First impressions and lessons learned • Keep it simple to start with • Security / Authentication: system libraries • Building, testing, reporting, monitoring etc is easier if you focus on a smaller set of tools • Have fun with it
Editor's Notes
- #4: If every service has to be updated at the same time -> not loosely coupled (nb: contracts) If you have to know to much about surrounding services (service envy) you're not bounded
- #7: Essentially the opposite of the monolith
- #8: deal with the shortcomings of the monolithic architecture
- #9: Systems grow in size and complexity, we start bumping our heads against issues such as scale and agility.
- #10: There are no bounds on the complexity of the app. As time increases so too: Increasingly complex code More LOC Larger database Business components become increasingly intertwined Deployments become rare, scary, complicated and take a long time. A large product team consisting of IT, development, QA, and deployment is responsible for building, maintaining, testing, and deploying such an application.
- #11: Get your ducks in a row. Remove or reduce the friction in the software delivery process. Standardization Contracts Error codes Base requirements (e.g.: api explorer, ping url, reliable testing data on staging, required test coverage .. etc) Libraries: Scaffolding Security / Authentication Base Testing Infrustructure: CI, automated everything, discovery + documentation but once your rich eco-system starts to take root, then we start to see the benefits
- #13: easy to make changes, lower risk
- #14: * Only deploy the parts you need to. Increased system resilience (lower risk) You know what changed - easier to debug
- #15: Scale the parts that need to Smaller components by nature (e.g.: natural database sharding)
- #16: Experiment with technologies Easy to throw away - localized technical debt Keep system up-to-date iteratively System resilience .. and the result of all this means that you can …
- #17: MicroServices are a technique that attempts to allow organizations to remain agile as they grow increasingly large and complex
- #18: Awesome: Give it CI, TDD, monitoring, beautiful documentation, an API explorer .. all that good stuff Become the agent of change Iterative - inception MicroServices. Provide your next business capability as a MicroService - consume it from your Monolith
- #19: Very much a work in progress! Open source, MIT
- #25: Discipline Testing Monitoring Orchestration Culture
- #26: • Page loads are significantly faster across the site Agility and speed: • Our development teams can develop and ship features faster and with fewer dependencies on other teams • We can eliminate redundant implementations of the same features in different countries where Groupon is available Also mention why now: automation tools, infrastructure as code, virtualization, + rise of JavaScript, multiple frontends (web, mobile, watch, desktop .. etc etc.) Small batches There are many benefits to micro: scalability, ... Etc. Today, I'm going to pick just one topic: how they lend to agility and speed.
- #28: Even though the ability to use horses for courses is an important factor of MS, when you start out, it is important that you get the most bang for your buck - so enable re-use, use your expertise etc. MVP: Once you’ve got the hang of it, you’ve got a good idea of what needs to be in place, and you have the systems in place to ensure things are as they should be, then you can get fancy!