What is a MICROSERVICE ARCHITECTURE and what are its advantages?

Studying For a Senior Dev role.

"It's called StackOverflow. I'm sure you've heard of it"

Me: NOPE. NEVER. All of my code just works immediately, always.

Really informative. Your explanation was clear, simple, and well-organised. Thanks.

you have awsome charisma man!
thanks a lot for the great explamation!!!

Gaurav, you should try for a teaching job. You teach really well.

I believe decoupling is not something only found in microservices. Infact even if it's a single process a good programmer has to deside on what the components of the system are and decouple them with interfaces. One could even do independent deployability in a monolith by having the system components built in dll files instead of having them built statically. A new developer doesn't have to understand the entire code, just the component they are working on and the interface contract on how it interracts with the other components.

very useful

Can a distributed system be a monolith? If so reduced network latency is not an advantage of monoliths.

Thanks Gaurav, this is perfect!!! Keep making such content! 🤟

Firstly, appreciate your efforts with this video. Besides the product roadmap, another key consideration is the cost of dev and maintenance. Any good matrices or stats you can research comparing these 2 archs?

I never understood what you call that in bewteen. Say you have an JS frontend, and maybe 2-3 APIs in .NET on different servers/machines.

That's not a monolith nor is it microservices?

All my life i worked on client side! these are gem concepts videos! thanks!

nice explanation bro

Now that's what I call method teaching. This is brilliant. Thanks for helping all of us.

One other advantage of using a microservice architecture is that trying out newer technologies means lesser pain as you can just rewrite one service without affecting the others.

very nice man, love it

1 con in a microservice architecture: there may be a lot of redundant code or the same code in different microservices to avoid RPC.

Successfully performed 32 post request to the db in my head in one go, you are awsome broo

Awesome explanation!! :)

Worst thing to ask after this video would be what is stack overflow? 🤣🤣🤣🤣nice video hatss off ♥️♥️♥️

Great video as always!

Monolith - Single/Multiple machine running the computation

Microservice - It's a division of whole works into business units which are turned into specific microservice.

Adv Monolith:
- Less moving parts
- Good for small teams
- Less duplication for tests etc
- Faster because everything is in same box(procedure calls)

Disadv Monlith:
- Require more context
- Deployment is complex (everything is touching every other thing)
- Too much responsibility on one server (one can break everything)
- Tight coupling

Adv Micro:
- Easy to scale
- Less context required
- Parallel development is easy
- Less hidden parts(more resources can be provided where it is required)

Disadv Micro:
- Tougher to design

Most of the times interviews are high scale and hence micro service is preferred

Thanks for video 😄

i Liked and subscribed. Thanks Gaurav

great videos and effort. subscribed to channel and been watching your videos to learn more about system designs in general. thanks for the content!

2023 and this video is still helping out! I'm just new in the software engineering world and yet you've managed to discuss monolithic and microservice systems in a way that even a newbie can understand. I also appreciate the references you've left in the description for further reading. Thank you for this.

Gaurav nice video, few questions:
1- How would different services be communicating in a Monorepo microservices architecture? Through APIs or different services functions call?
2- Can services in monrepo be still in different languages or it's just for polyrepo?

I have worked on both and the video quite summarize the experience one have. The "New Member" in a team point was quite right!
Amazing work! Thanks!

"Where is nothing micro about microservices" - loved it :))

Great content. Could you please make a video on microservice intercommunication?

This is great, thank you for your work 😌

At 5th min , you were saying that new developer needs to know abt just the service he works on… you are wrong…. Dfltly knowledge of other services is must to work on x service for any new developer otherwise chance for errors by him

thanks for the presentation and explanation.

that's why stack overflow goes down entirely sometimes due to its monolith architecture interesting

First in monolith you said deployment is easy because everything is at one place, then you said it's hard as we need to touch a lot of things. Again for micro services you said design is easy because each server is handling only one thing, then it was like design is hard. Could someone explain?

Your channel is the best place to learn backend engineering 🙏

I am preparing for my upcoming interviews and these videos are helpful

Unpopular opinion :
Microservices Architecture is like running an ICE engine car, while monolith is like an Electric.

Before coming with pitchforks😂, just give it a deep thought.. More moving parts, expensive transfer of energy(data)... Many more comparison points

I reada bunch about Google using monolith architecture to store their code internally, whereas they also have GCP available for selling microservices. If GCP is good (cough cough), Why do they not use their own product? Sounds ambivalent. PS Google, if you're listening, I didn't mean to offend you, I am ignorant and learning. :)

Monolith is not single point failure.I think single point failure is different thing.

Can we have a sample problem like designing an ecommerce system or food delivery system and design all the microservices needed in it from scratch?

Super clear explanation. Thank you :)

I think we can use a combination of monolithic and microservices architecture.

Good video 💯

Full marks for the thumbnail😂

Thanks!

Such a good video!

nice concept