The 6 Rules for Modernizing Your Legacy Java Monolith with Microservices
30 likes9,443 views
The document outlines six key rules for modernizing a legacy Java monolith into microservices, highlighting the benefits of microservices such as scalability, resilience, and independent deployment. It discusses principles of domain-driven design, async messaging, and transaction management in distributed systems, as well as tools like Play and Akka for implementation. Additionally, it offers guidance on API management, dependency management, and event sourcing, concluding with a promotional note about Lightbend's services for transitioning to microservices.
The 6 Rules for Modernizing Your Legacy Java Monolith with Microservices
- 1. The 6 Rules for Modernizing Your Legacy Java Monolith with Microservices by Kevin Webber (@kvnwbbr)
- 13. heritage architecture » Single points of failure » Impossible to scale out (shared mutable state, etc) » Different non-functional requirements (reads, writes, compute) » Optimized for none! » Long, risky release cycles
- 25. Microservices » Ubiquitous language » Well defined models & boundaries » Single responsibility » Independently deployable, scalable, resilient » Communicate via async messaging » Own their data » Don't expose a public API
- 26. Approach? Principles » responsive, resilient, elastic, message-driven
- 27. Approach? Principles » responsive, resilient, elastic, message-driven Concepts » bounded contexts (DDD), event sourcing, CQRS, CAP (eventual consistency)
- 28. Approach? Principles » responsive, resilient, elastic, message-driven Concepts » bounded contexts (DDD), event sourcing, CQRS, CAP (eventual consistency) Tools » Typesafe Reactive Platform (Play, Akka, Spark)
- 29. Conceptsand patterns We will cover: » Domain Driven Design (DDD) » Async messaging » API management » Dependency management » CQRS & event sourcing » Transactions & ordering
- 36. Getting started » Model sub-domain at package level » Tip: Visualize existing architecture with a tool like Structure101 » Define public RESTful API at package level (use async messaging inside package at service level) » Refactor for physical separation, remove package
- 37. Goingasync
- 42. Async Benefits » Not wasting resources » Memory, CPU, threads » Embracing failure » Not expecting a return from a remote service » Designing for all scenarios
- 43. API management
- 55. API mgmt. » Messaging patterns » Pub/sub, point-to-point, streaming » API gateway » Routing, aggregation, protocol translation » Discovery » Service discovery, registry, versioning
- 73. Considerations » ACID doesn't work across location/trust boundaries » No 2-Phase commits (2PC) » No holding locks for the duration of work » In distributed systems we need to compensate for for failure rather than prevent failure
- 76. Whatnext?
- 82. Microservices with Lightbend » Play for API gateway » Akka for core microservices (DDD, CQRS, event sourcing) » ConductR for cluster management (service registry, discovery, architecture visualization, security)
- 83. Lagom Monolithto microservices » Webinar: March 17, 1PM PST / 4PM EST » https://www.lightbend.com/discover-lagom » Ready-to-use connectors: event-sourcing, CQRS » Launch all microservices with a single command » Instantly visible code updates
- 84. Thankyou! Visit https://www.lightbend.com/products/lightbend- reactive-platform to get started Contactinfo » Twitter: @kvnwbbr » Email: [email protected]
- 85. LIGHTBEND REACTIVE PLATFORM Full Lifecycle Support for Play, Akka, Scala and Spark Give your project a boost with Reactive Platform: • System orchestration for resilient releases • Real-time monitoring of asynchronous systems • Self-healing for network partitions, node and apps • Availability protected with configurable user quotas • Certified, load-tested Reactive Runtime Enjoy learning? See about the availability of on-site training for Scala, Akka, Play and Spark! GET STARTED