Talk about why monoliths are not supposed to be evil, how not to make them evil, how to know the right time for decoupling monolith into microservices.
3. No PHP, #bummer
But we can chat about it later and I will mention few things about
what we do and how.
But I must say, lot of things are pretty generic, no matter the
programming language.
9. Monoliths are big and strong
..and maybe bloated.
But what does it mean? How does it look like?
10.
11. Big ball of mud
..is something you don’t want.
Ever.
12.
13.
14.
15.
16. Monoliths or microservices, it
may still end up in the same hell
hole
Or not, but you really have to design your application first hand.
17. All the musts for M/SOA are
valid for every software project
Documenting! Testing! Loose coupling! No shortcuts! No hacking!
Good SW design! Separation of concerns! Fast deployments!
Continuous integration! Monitoring! Caching! Other stuff!
18. Is it really binary (or black and
white for nontech) problem?
It is not.
37. More reading… (and watching)
Microservices, monoliths and laser nail guns: Etsy tech boss on finding the right focus
https://medium.com/s-c-a-l-e/microservices-monoliths-and-laser-nail-guns-how-etsy-finds-the-right-focus-in-a-se
a-of-cf718a92dc90#.m2jxzcb0l
Modular Monoliths - Simon Brown
https://www.youtube.com/watch?v=k8bi2r6Z0h8
Microservice Trade-Offs - Martin Fowler
http://martinfowler.com/articles/microservice-trade-offs.html
Modular vs Monolithic: No Holy Grails
https://speakerdeck.com/pote/modular-vs-monolithic-no-holy-grails
MonolithFirst - Martin Fowler
http://martinfowler.com/bliki/MonolithFirst.html