Modular Monoliths Gotopia Tech Gain insights into the transition from monoliths to microservices in this book club episode. modernize your tech stack. Using graph theory and network science to explore your microservices architecture goto copenhagen 2019 40:29.
Goto Conferences Tech And Software Events Learn Grow Gotopia Tech Microservices have become more than a buzzword and are now viable alternatives to monoliths, which makes understanding why and how they should be used more important than ever. thinking strategically about software architecture has to be the cornerstone of any software development. In this presentation, i describe the dark energy and dark matter forces (a.k.a. concerns) that you must consider when deciding between the monolithic and microservice architectural styles. As a companion to sam newman’s extremely popular building microservices, this new book details a proven method for transitioning an existing monolithic system to a microservice architecture. Interview with erik schön, author of “the art of strategy” goto bookclub – where tech enthusiasts come together to explore the latest tech reads and engage in stimulating discussions.
Moving Beyond Monoliths And Microservices Gotopia Tech As a companion to sam newman’s extremely popular building microservices, this new book details a proven method for transitioning an existing monolithic system to a microservice architecture. Interview with erik schön, author of “the art of strategy” goto bookclub – where tech enthusiasts come together to explore the latest tech reads and engage in stimulating discussions. But now, in 2025, a surprising trend is emerging—some of the same companies that embraced microservices are stepping back, merging services, or even returning to monoliths. I have distilled these guides from the lessons i’ve learned making the journey to microservices in different domains. the experience is drawn from domains such as finance, telecommunication, supply chain and retail. It doesn’t matter if it’s a monolith, a modular monolith, or carefully chosen microservices. what matters is that your architecture meets the needs of your users and gives your team the tools. This allows organizations to choose from varying tech stacks and cherry pick the ones that best suit each of their microservices’ business requirements; instead of relying on one stack for everything (like in monoliths). easier to understand and finally, microservice architectures are easier on the brain.
Comments are closed.