A very good https://www.youtube.com/watch?v=ILXcsNxbas4 about complexity.
This video https://www.youtube.com/watch?v=0HqUYpGQIfs on complexity gave me some interesting thought-provoking insights.
Great video, thanks!
I watched it, the video was obviously AI generated but that's ok 😄. Imo what's missing that I see in the wild again and again: • 1 service == 1 repo, this introduces versioning problems, shared libraries, complex tooling, makes it harder to debug your code and iterate... • Defaulting to synchronous http between services instead of message passing, creating tight coupling and systems that easily break • Schema versioning complexity (making non-breaking changes is not always obvious for the avg enterprise dev) • creating a proxy layer of microservices with http on-top of the old system instead of using e.g. CDC and creating a standalone system that is not tightly coupled with the old. When the legacy system is down for maintenance, nothing works. The other things that were mentioned in the video are very valid.
Good points, including that it was AI-generated!