Jakub Nabrdalik - What I wish I knew when I started designing systems years ago

I started designing systems (also known as: architecture) 19 years ago. I'm not very smart, so I've made a LOT of mistakes on the way. Surprisingly it turned out these are quite common. I'd like to share a few things I’ve learned that would save me a lot of tears, had I known better back then.
I’ll talk about communication styles, how to design good modules, SLA, invariants and events, choreography vs orchestration, single point of truth vs data ownership, products vs projects.
This talk is for people starting with software architecture or anyone wondering about whether their next project should be REST microservices, Event Driven or a modular monolith.
Slides: jakubn.gitlab....
Want to get notifications about future meetings? Join us at devflix.pl

[@RadoslawSzymanek]

I work with large code base based on "micro" service approach. We have quite a lot of services that are based on data (not like user service), but still data. However, this data is not like user data needed everywhere. Therefore, I wonder if depending on the data nature maybe some microservices based on data makes sense. I definetely work with some data based microservices and I am happy that they are done like this. I would not like to have this data duplicated in many micro services, it will feel much more harder to maintain and evolve solution.

[@roman_mf]

I'm only 30 minutes in, but already got enormous value out of the presentation. Excellent talk!

[@JuniorJavaReady]

So good :)

[@DevelopersWorldAcademy]

Thanks! 😄

[@Cybuch44]

Great talk Kuba!

[@DevelopersWorldAcademy]

Super cool you like it!!!