Microservices: are they worth it?

Deep dive into microservices, how this architectural pattern came about, the journey through service oriented architecture, what problems it tries to solve and some of the issues that come as a consequence of implementing it this architecture!

▬▬▬▬▬▬ Resources & References 📕 ▬▬▬▬▬▬

▬▬▬▬▬▬ Chapters 🕐  ▬▬▬▬▬▬

00:00 - Intro
00:22 - Why monoliths don't scale
03:27 - Service Oriented Architecture (SOA)
04:23 - Microservices
06:29 - The good
07:32 - The bad
13:46 - Conclusion

▬▬▬▬▬▬ Connect with me 👋 ▬▬▬▬▬▬

▬▬▬▬▬▬ Support the channel 💜 ▬▬▬▬▬▬

Every little bit helps ✨

#glichstream #softwareengineering #programming #coding

[TheCameltotem]

Oh boy. I've been in this micorservice trench for 2 years now and while I do love the simplicity of the actual business logic being contained in one context and the idea of owning a few services yourself.

Microservices are HARD. When starting out you don't even know the full business domain, the requirements, the potential bottlenecks or even at what scale you will be running. To design a system with these unknowns in advance is pretty much impossible.

There is also a whole slew of more work regarding infrastructure and actual data transportation, you are replacing in code calls to external calls and that comes with it sets of problems and time consumption.

I'm having a lot of fun but I would not suggest anyone to start out with microservices, instead build a cloud first monolith or SOA system and see where that takes you. Scaling in the cloud is so easy these days, you might never need microservices.

[jaafarnasrallah]

The sigh and smirk at "books, seminars, videos..." 😂

[alikaraki]

Took so many notes, thank you for sharing your insights

[jaafarnasrallah]

If I may just add to that, in the cons. To share my experience and hopefully get your feedback as well.

1.Something that all "new trends" share. We can't run from bad engineering practices and models into just adopting the new thing as a resort.

2. In the authorization part, we kidna managed the IAM when the team was 3 people, two lines under kinda. On expansion we had to have a clear structure of permissions. And IaC turns from a luxury to a must have or else some team members are going crazy

[xa]

A lot of useful information in only 15 minutes! ❤

[eddywa]

Wonderful summery! Yet not a one size fit all summery imo…. Just from a theoretical pov you’re totally right, but certain business areas with very very complex usecases just benefits of an microservice architecture since this is key to break down complexity actually while maintaining a variety of possible customer usecases which are consuming a microservice

[GringoDotDev]

This is such a balanced and informative take. Great video!

[stripmaker]

I do not like microservices, but that might be because my studies forced them together with learning DevOps. We did not get a very clear introduction of either and were expected to just figure it out on our own. This video has taught me more on the subject than 10 weeks of struggle with an unclear assignment, which is kinda sad.

[SiiitiiFreelancing-jlty]

Banking apps developed years ago just cannot be redeveloped the Microservices way

[mhadi-dev]

One of my the first encounters with Microservices was not actually microservices, it wan Nanoservices.