Microservices (often deservedly) get a bad rap: they create complexity and introduce a new class of problems that are hard to solve. But what happens when you legitimately need multiple services to perform disparate tasks in your infrastructure? Come learn about the "monolithic microservice", a new architecture for separating service concerns and offering a middle ground between the monolith and microservice.

Comments

Please login to leave a comment

No two projects are exactly the same, and the size and past experiences of teams will often dictate how we feel about monoliths v microservices v something else entirely. I really appreciated Sarah's approach to finding that happy middle-ground where teams can get the benefits of a monolith with the flexibility of microservices. She was also really great about explaining when monolithic microservices might make sense (based on app size/complexity, team size, application maturity, etc.)—and when they don't.