Session

7 Strategies for Building Majestic Monoliths

“You shouldn't start a new project with microservices, even if you're sure your application will be big enough to make it worthwhile.” - Martin Fowler, who coined the term “microservices” (https://martinfowler.com/bliki/MonolithFirst.html)
In this talk we will follow Mr. Fowler’s advice and build a Majestic Monolith (https://m.signalvnoise.com/the-majestic-monolith) that can easily be refactored to microservices if and when the need arises.

We will look at 7 strategies for successful majestic monolith building:
* Using Domain Driven Design and Bounded Contexts
* Putting API’s first
* Making data autonomous
* Avoiding bottlenecks
* Committing to continuous integration
* Embracing and measuring code quality
* Adopting the Citadels and Outposts pattern

Of course tools are required to implement strategies, and in this talk we will use Quarkus, the Supersonic, Subatomic Kubernetes Native Java Framework, but you will be able to apply these strategies with almost anything

There will be a bit of live coding and a lot of code available on GitHub

Jeremy Davis

Solving things, slinging opensource

Decatur, Georgia, United States

Actions

Please note that Sessionize is not responsible for the accuracy or validity of the data provided by speakers. If you suspect this profile to be fake or spam, please let us know.

Jump to top