What is microservices architecture?

What are microservices architecture? Why do we use microservices? How do microservices talk to each other? How do we test microservices? What are the problems with microservices?

#microservices

▬▬▬▬▬▬ Timecodes ⏱ ▬▬▬▬▬▬
00:00 Intro
00:25 What are microservices?
05:09 Why do we use microservices?
07:17 How do microservices talk to each other?
09:07 How to test microservices?
11:38 What are the problems with microservices?
14:40 Are you really having microservices?

▬▬▬▬▬▬ 🚀 Courses, books, and podcasts 🚀 ▬▬▬▬▬▬

▬▬▬▬▬▬ 👋 Contact me 👋 ▬▬▬▬▬▬

[DevOpsToolkit]

How do your microservices look like? How different is what you're doing from what I explained?

[thescourgeofathousan]

Viktor, I think I love you.
I’ve spent so long arguing fruitlessly with dev teams of clients trying to explain this.
It has been terribly lonely and dejecting.

[Drrpheus]

Please keep these videos coming!! They are the best cases I can send to my clients to answer their questions and issues in under twenty minutes!

These are knowledge sharing gold, my friend. And the rest of the devops community should be celebrating this material.

[aleksandrarestov]

Unfortunately, in all organization where I worked, microservices is distributed monolith. Devs think that if they use Kubernetes that it is a silver bullet. But in reality, every release may break another app.

[AndreiDinTheHouse]

Very concise! I also found that 98% of the time when people say they hate microservices and they don't make sense, they in fact dealt with a distributed monolith and lost the challenge of synchronizing deployments to fit the coupling. The other 2% they failed to tackle the operational overhead inherent to adoption - usually because the adoption was done under some kind of pressure and was haphazardly put together.

[ChristofferVig]

Thanks for another entertaining and enlightening video Viktor! So, as I now see this, before you start creating a microservice, you should think and plan out the interactions of the complete system, divide into domain entities that can be said to have a single responsibility, and sketch out the required inputs and outputs. Next up, define the data model. With the data model in hand, you may now engage in the microservices journey. The data model should be tailored for the communication layer, internally each service may use different models.

You cannot simply start to create a microservice. You have to plan the interactions of the system first.

[stef]

Straight to the point, explained in a concise, but warm way. You are incredible! Thank you.

[matscloud]

Great video, again. It's a bit sad how the entire industry jumps into a tendency most people don't understand. Devs are not to blame... Their bosses are, forcing them to do microservices just cause the others are, without understanding the benefits, the risks or the complexity.

[GeertBaeke]

I know one thing: I wouldn't want to argue with you about it! 😀 Great video.... and a reflection of reality (sadly)...

[GuillaumeMaka]

The hard part with microservices for me was testing. Like what to test without going outside of the context boundaries of a microservice. But with practice its achievable. Question for your regarding microservice code base organisation:

will you suggest:
- microservice per repository
- monorepo with all microservices + some monorepo management tools (like Bazel)

[andrepires]

Great Video, thanks Viktor,
I would like to know more about testing using mock data. For example how to set up mock data from an API using its openAPI.

[thinkdevops]

Awesome video! I fully understand that you can't stay calm with this topic, I gave up on arguing about it. :/
There are great resources out there to share info about what micro service architectures are and with your video there is one more!

[gigiduru]

All devs should watch this video and also listen. I truly don't understand their thought process when they are splitting their stuff where they have like 5 services per developer and basically just replacing local function calls with network rpc.

But hey, if they just had like 2 services they wouldn't need kubernetes and I wouldn't have a job so I'm not complaining 😂

[momusi.]

Thank you for the clarification between distributed monoliths and microservices. As it turns out, I was building distributed monoliths hoping to get the benefits of microservices. The video leaves me confused thought, because I cant imagine a scenario where the system as a whole is a collection of microservices that are "all" loosely coupled. In such a scenario, would not each microservice for example do its own persistent storage (DB) authentication and authorization, logging and much more? I would imagine that there is something like a "core" or platform that itself is maybe a monolith or a distributed monolith that provides services to those microservices. Do I miss something?

[dmytroshchotkin]

It's a nice passionate speech! =)

[EmilDafinov]

"We do not create a microservice that is communicating with the database" 😭😭😭😭😭😭😭😭😭😭😭😭😭😭😭 Why, oh why does every employer ask me to do that then😭😭😭

[benitoprijs]

Very recognizable, thanks again for this fun video! Cool t-shirt btw...

[Nilesh_Narkhede]

Hi Victor,
Really great explanation. Thanks for putting it all together.

I am confused in between API Gateway and service mesh. I would like to ask you Where exactly service mesh fits into microservices architecture?

API gateway is also handling cross-cutting concern and service mesh also does that by implementing sidecars for individual microservices. If we introduce sidecars, Wouldn't it increase extra operational complexity ?
And which component companies using in production for handling common concerns ?
What is your opinion on above points ?

[S]

What are the security challenges in creating a microservice in line with the principal of devsecops?
Can we have a separate video on it

[chandup]

Awesome explanation. Thank you.
Could you explain how to write functions as service (function as code) using openfaas & explain difference between FaaS and Microservices, please