Microservices Minus The Hype
0 likes444 views
The document discusses the impact and structure of microservices compared to traditional monolithic architectures and service-oriented architecture (SOA). It highlights the benefits of microservices, such as improved scalability, efficiency, and reduced coupling, while also noting the increased complexity they can introduce. The author emphasizes the evolutionary nature of microservices, differentiating them from SOA and providing insights into their implementation and operational needs.
Microservices Minus The Hype
- 1. Microservices Minus the Hype How to Build and Why Mark Heckler Principal Technologist/Developer Advocate Pivotal Software, Inc. www.thehecklers.org mark@thehecklers.org @MkHeck
- 2. @MkHeck #microservices @ThatConference Who am I? • Author • Speaker • DEVELOPER • Survivor of many monoliths • Seeker of a better way • Java Champion
- 3. @MkHeck #microservices @ThatConference The Goal: This
- 4. @MkHeck #microservices @ThatConference The Goal: Not This
- 5. @MkHeck #microservices @ThatConference The Goal: This
- 6. @MkHeck #microservices @ThatConference The Goal: Not This
- 7. @MkHeck #microservices @ThatConference THE Goal Velocity
- 9. Monoliths That’s one big app!
- 10. @MkHeck #microservices @ThatConference Characteristics • Single logical executable • Shared data across functionality • Control flow change impossible • Non-granular app modification • Non-granular scaling • Attachment to language, platform • Low cohesion, high coupling • Failure of part == failure of whole* • Mental model “complete” for smaller systems
- 11. Microservices Assemble to make “more than meets the eye”
- 12. @MkHeck #microservices @ThatConference Characteristics • Independently deployable & executable • Focused services • Control flow changes trivial • Non-disruptive change • Effective & efficient scaling • Polyglot “Plus” • High cohesion, low coupling • Failure is isolated • Manageable mental model
- 13. WAIT! Isn’t this just warmed-over SOA?
- 14. No
- 15. @MkHeck #microservices @ThatConference SOA vs. Microservices • Conceptually similar • Implementation draws clear distinction
- 16. “…the microservice style is very similar to what some advocates of SOA have been in favor of. The problem, however, is that SOA means too many different things, and that most of the time that we come across something called ‘SOA’ it’s significantly different to the style we’re describing here, usually due to a focus on ESBs used to integrate monolithic applications. … This common manifestation of SOA has led some microservice advocates to reject the SOA label entirely, although others consider microservices to be one form of SOA, perhaps service orientation done right. Either way, the fact that SOA means such different things means it’s valuable to have a term that more crisply defines this architectural style.” Martin Fowler, “Microservices and SOA”
- 17. “Microservices is an evolution of SOA concepts that can provide additional benefits to adopting organizations. The benefit of Microservices over ‘traditional’ SOA is speed and agility for making changes, and the ability to make changes with less overall cost and less impact on the existing infrastructure. Microservices involves a different approach, as well as some different uses of technology.” “The Great Debate: Microservices vs SOA”
- 18. @MkHeck #microservices @ThatConference • Dumb endpoints, smart pipes • Smart endpoints, dumb pipes SOA vs. Microservices • MACROservices • Heavier: SOAP + XML • More coupled ceremony • This makes it much more difficult to scale • More focused (but more of them) • Lighter: REST, XML or JSON • Low ceremony, low coupling • Built to scale SOA Microservices • Orchestrated • Choreographed
- 20. @MkHeck #microservices @ThatConference Microservices Architecture Gains • Scalability • Efficiency • Effectiveness • Velocity • Optimization • Availability • Independence • Cost savings • Increased revenue • Interoperability • Less complexity* • Control
- 21. @MkHeck #microservices @ThatConference Microservices Architecture Losses • Greater complexity (macro level) • Better architects needed • Single data repository for organization • Change…seriously • Greater complexity - it bears repeating
- 22. @MkHeck #microservices @ThatConference The Play-DohTM Principle Applies Microservices
- 23. @MkHeck #microservices @ThatConference The Play-DohTM Principle Applies Monolith
- 24. @MkHeck #microservices @ThatConference The Play-DohTM Principle Applies It's always easier to combine small, self-contained code or data than it is to decouple code or to parse data.
- 25. What Do I Need to Execute?
- 26. @MkHeck #microservices @ThatConference Microservices: An Example
- 27. @MkHeck #microservices @ThatConference Config Service
- 28. @MkHeck #microservices @ThatConference Service Discovery
- 29. @MkHeck #microservices @ThatConference Client-side Load Balancer
- 31. @MkHeck #microservices @ThatConference Circuit Breaker
- 32. @MkHeck #microservices @ThatConference Circuit Breaker Dashboard
- 37. @MkHeck #microservices @ThatConference Thank You for Participating! • Helpful Links • 12 Factor apps: 12factor.net • Spring Initializr: start.spring.io • Cloud Foundry: cloudfoundry.org • Pivotal Web Services: run.pivotal.io • Example projects: https://github.com/hecklerm Keep the discussion going on Twitter! @MkHeck