Lesson 162 - Microservices Architecture

[@rehmansaifmohd]

Just too good Mark. All the struggle looking for architecture stuff is now gone with your lectures. Amazing

[@markrichards5014]

Thanks!

[@rahulsaha3569]

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.

[@MrDomenic123]

Then you wanna make sure to also read his books that he wrote with Neil Ford. Highly recommend the reading 👍

[@markrichards5014]

Thanks and I'm glad you are finding it useful

[@muratcengiz9235]

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

[@markrichards5014]

Yes, I would agree. That's where transactional sagas come in. Sync/Async, Choreography/Orchestration, and Atomic/Distributed Transaction all play a role.

[@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?

[@andriisnihyr6497]

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. :(

[@sant4398]

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.

[@markrichards5014]

MS is definitely not a subset of SOA. I wrote a book on this exact topic - you can get a PDF download of it here: www.developertoarchitect.com/downloads/microservices-vs-soa.pdf

[@shashikumaarb]

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

[@yar697]

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?

[@markrichards5014]

It can be, but remember you have a broader bounded context, meaning a change to the table impacts BOTH services

[@GregoryBates]

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

[@GregoryBates]

PS: Your videos have really helped me expand my technical breadth over the last couple of years. Thank you!

[@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)

[@sant4398]

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. )

[@markrichards5014]

Yes, you are correct about the API Gateway, which is why I like to federate the gateway by domain when I can. In other words, have a customer gateway, order gateway, fulfillment gateway, and so on. It helps address the single point of failure. I often do the same thing with physical databases as well as message busses and brokers. Regarding performance, if you have a system that doesn't communicate between services, performance os good. However, that sort of system is rare. In most systems services communicate with each other to get data and also perform functions. That's why we rated performance low in microservices.

[@ianhamilton8376]

The Microsoft architectural dichotomy: monoliths and micro-services. Appears in MS docs from about 2016, when micro-services had become popular, but no-one in their right mind would do them in Visual Studio. Answer: redefine micro-services to be something that could be done with VS.

[@An7Hoang]

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

[@markrichards5014]

Many watch my videos directly from my website at DeveloperToArchitect.com, which also has other resources as well.