Nowadays everyone is talking about microservices and how cool they are. That's true, but not all business needs to move to microservices, you can still use monolith architecture and make it more fashion by applying some of the design/elements that you've learned from microservices architecture. Can you use circuit breaker pattern, service isolation, event-driven and non-blocking application, cloud-native approach or zero downtime deployment in monolith architecture? Is it worth? The answer is YES!!!. Come to this session to learn how to make your Java monolith applications attractive again by borrowing some of the principles of microservices architecture.
7. @alexsotob7
… due to the given burdens of cost and organisational maturity,
microservices will likely never reach the Adopt phase“ Rebecca Parsons - CTO at ThoughtWorks
14. @alexsotob14
Isolation of Data
game schema
Game
Detail
detail schema
Reviewreview schema
Module == Schema
Joins inside Schema
Referential Integrity across Schemas
Global transactions
flyway, liquibase
22. @alexsotob22
Your Stack Matters
Server Hardware
Operating System
Application Server
your.war
Java Virtual Machine
Custom Configuration
Linux Kernel Version & Distribution
Java 1.7.0_67
Tomcat, Wildfly, Jetty
JDBC driver, users
33. @alexsotob33
Advantages of monolith
> Local Calls
> All parts always up
> Easy to debug
> Easy to test
> Refactor without running surprises
> You see the real world every time
> Easy to deploy (coordination)
> Polyglot Languages, DB