Lesson 162 - Microservices Architecture

Continuing with our journey through various architecture styles, we are now going to look at the other side of the spectrum—distributed architectures. Continuing the same pattern as before, I’ll start by describing a little bit about the core concepts of the microservices architecture style, then talk about its strengths and weaknesses and explain when you should use it, and when you should avoid using it.

Reference Links:

[rahulsaha]

I recently started following your content. Its simply amazing and was just what I was looking for as a IT professional. Thank you so much for the amazing service to this community.

[muratcengiz]

Transactions spanning multiple services (and patterns for handling them) must be the biggest contributor to complexity i believe. great content as always..

[andriisnihyr]

As usually great video, thank you! Special thanks for taking the time and talking about when not to use microservices. One of the projects I worked on recently, failed, as me and my colleagues failed to convince our leadership to not use microservices as it will kill the performance due to multiple inter-service calls. :(

[GregoryBates]

I’m taking the phrase “big ball of distributed mud” to work with me tomorrow!

[HemalVarambhia]

I infer that micro services manage their own state (much like an object would) and thereby tighten encapsulation (which appears to scale). I also realise from your video that a DDD context map would useful when we appeal to micro service, identifying the relationships (OPEN HOST SERVICE, CONFORMIST, SEPARATE WAYS) between them.

It's interesting that you discuss Agility and I'm reminded of Kevin Henney's presentation on Architecture and Agility: Married, Divorced or just good friends! What's your view on Architecture and Agility?

[yar]

Hi, Mark! Hope you are good.
One more question from me.
If i share one table by two MS, but one is reader, other is writer, is it convenient for MSA?

[MrKZee]

I will start from the bad: the sound
some low-tone ramble through the video was triggering me))
I would ask and advise to user a high-pass filter (cut-off sound below 50-100 Hz) or run some denoiser plugins.
But the high-pass exists almost in all software for video editing too, so I would ask to use it, please)))
By the way, love your books and lessons)

[shashikumaarb]

Sir can you let me know some of the technologies available for api layer?

[AnHoang]

I forgot how I subscribed to your Youtube channel but your delivery and knowledge is top-notch. Maybe your audience is not primarily on YouTube? Do you have a community elsewhere?

[sant]

What is interesting, the Wikipedia says that "is a variant of the service-oriented architecture structural style". Means they consider it as a subtype of SOA.

[sant]

Thanks for the new lesson! Couple questions: Isn't the API Gateway the single point of failure? And not a question, but rather observation. As I see nowadays many architects tend to call the "microservice architecture" everything what is distributed and is not a monolith. I recently took part in one architecture conference and paid attention - speakers don't recognize other architecture styles, except monolith, microservices and event-driven. It come to absurd when one speaker presented a slide where recommended to use microservices in case we need "performance". Or, maybe, I don't get it right, so, please, correct me. )