Tomas Strejcek discusses the pros and cons of monoliths versus microservices, emphasizing the importance of good software design principles such as documentation, testing, and separation of concerns. He argues that while microservices can be beneficial, starting with a monolith might be more practical and highlights the challenges of managing multiple microservices within a small team. Ultimately, the key takeaway is that developers should prioritize effective architectural design over the choice between monoliths and microservices.

1. monolith vs microservices vs team
Tomáš Strejček, Dev Leader, Mall Group
@TomasStrejcek

2. aboutme.md
MallGroup, Rockaway, RocDevs, Stuff

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.

4. Don’t take me too seriously
No, really. Don’t.

6. I will not tell you what is better
..but I will show you stuff that matters

7. I won’t show you how to do M/SOA
..you can google that sh**

8. Monoliths are #evil
Not!

9. Monoliths are big and strong
..and maybe bloated.
But what does it mean? How does it look like?

11. Big ball of mud
..is something you don’t want.
Ever.

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.

19. 3mw architecture slide

21. How hard is to find what is
going on?
Are monitoring tools and logs enough? Do you have API?

22. Microservices are great, but you
need to GET there, not START
there.

23. #MonolithFirst
Is then M/SOA last?

24. Monolith -> ? -> M/SOA
? = time or something else

25. Modular distributed
monolith architecture
MDMA for short
I made it up obviously but it really made me laugh, so I am rolling with it.

27. What I mean is..
..wait for it ..

28. Is application different when
run in CLI instead over FPM?
It should be.

29. Is application different when
you access it through user
backend or user frontend?
It should be.

30. You, as developers, have great
power to change you app
behavior via configuration.
Incl. feature flags, environment variables etc.

31. How do you maintain 20
microservices in team of 5
developers?
You can’t and you shouldn’t get to the point where you do.

32. Managing, deploying and
scaling complexity is hard.
But deploying single app? Just git pull and adios.

33. Everybody doesn’t have to be
DevOps
Not even those fancy react redux nodejs javascript hybrid guys
rolling on AWS.

34. Infrastructure as a code to the
rescue!
Or not, you don’t really need IaaC in monoliths.

35. What really matters: does it
work? :)
(for you)

36. Thank you!
Questions?
Tomáš Strejček, Dev Leader, Mall Group
@TomasStrejcek

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