An Accurate Explanation of Microservices

It's a loaded and nuanced term. Here are some things that don't get explained very well, or at all, when talking about the Microservices Architecture... all of course in my own opinion.
Chapters
0:00 - Intro
1:20 - The purpose of microservices
1:41 - Why devs choose microservices
2:43 - Events should be first-class citizens
3:37 - Database per service - but why?
6:13 - Cross cutting concerns are tough
7:03 - CAP Theorem
8:33 - Why you should start with a monolith
10:25 - Microservices aren't bad, just used for the wrong reasons

[@edrose5045]

You've hit the nail on the head with this.
Microservices ALWAYS add complexity to a project, but that complexity cost MAY be worth it in a specific use case.
Personally I see far more value in the technical scaling benefits of microservices than the managerial aspects of splitting the code off into teams. A well structured monolith is just as easy to segment into different teams as a microservice - facebook actually uses a single repo for every single project they have, so it's not like you need a repo for each team

[@Olfan]

To my mind, microservices try to do what object orientation should have done. The object/service is the sole owner of its data and knows what to do with it. Objects/services can send each other messages and hand over new data, ask for existing data or ask to perform actions on some data. Mind that other than with object oriented languages the distinction between objects/services and their data still works - nobody (yet?) demands that every piece of data be their own microservice.

[@ShikaIE]

Great video! Do more of topic like this!
One suggestion I’d add is maybe to add some visuals / examples etc.

[@bc4198]

I just came in here to say the same thing! 😊

[@elijahmcphersonmelton6136]

very good video! keep them up

[@Masqueey]

"...and getting more subscribers helps me feel better about myself." LOL 😂