InfoQ Homepage Modular Monolith Content on InfoQ
News
RSS Feed-
Spring Modulith 1.0 Gains Production-Readiness, IDE Support and Improved Testability
Spring Modulith 1.0 was promoted from its experimental status and became a fully supported Spring project. It structures Spring Boot 3 applications through modules and events. That module structure is now visible in IDEs like Spring Tool Suite and Visual Studio Code. The Event Publication Registry persists event completion faster. And Integration Tests Scenarios ease testing events.
-
Google Service Weaver Enables Coding as a Monolith and Deploying as Microservices
Google has released Service Weaver, an open-source framework for building and deploying distributed applications. The Go-based framework includes a set of programming libraries that enable writing applications as a single modular binary. The other component is a set of deployers that allow for configuring the runtime topology and running the application locally or in the cloud.
-
Spring Modulith Structures Spring Boot 3 Applications with Modules and Events
VMware shipped the experimental Spring Modulith project to better structure Spring Boot 3 applications with modules and events. The project introduces new classes and annotations but doesn't generate code. Modules map to Java packages and are encouraged to use Spring events which can be automatically stored in an event log. Spring Modulith also eases the testing of modules and events.
-
Decomposing a Monolith Does Not Require Microservices - Sam Newman at QCon London
Sam Newman says the goal of decomposing a monolith must be independent deployability, and developers need to focus on the outcome, not the technology. Speaking at QCon London, he said, "The monolith is not the enemy" and, "Microservices should not be the default choice."
-
To Microservices and Back Again - Why Segment Went Back to a Monolith
When Segment moved to a microservices architecture, they gained environmental isolation, but at a cost of higher operational overhead. Three years later, the costs were too high, and the team migrated back to a monolith. At QCon London, Alexandra Noonan told the cautionary tale, and emphasized the importance of evaluating trade-offs in architectural decisions.