MICROSERVICES ARCHITECTURE | MONOLITHIC ARCHITECTURE | PART - 2

[@VikrantVerma22]

Adding to the disadvantages for monolith: - whole server crashes when one of the module fails/throws exceptions. eg non-runtime module fails because of some reason and brings down the whole website. - if we know a module is bottle neck, we still have to scale up the whole system, as we cannot scale up just that module alone.

[@qasimmavani]

excellent information.thankyou!

[@Saintura1]

Your teaching is simple

[@vigneshsoap123]

I think there are some points to support Monolith like 1. Microservices need to talk to each other through n/w packets. Monolith is mostly IPC and hence faster. 2. Monitoring all the Microservices (100s) and checking their health to ensure smooth running is a pain. 3. Monolith need not worry about consistency since they primarily operate on the same data store. 4. Monolith in general have better latency since the non-determinism of microservices is not present.

[@321zipzapzoom]

Hi Vignesh,to compensate for above mentioned latency factor, edge computing comes into play.

[@aashish01yash]

Good Points

[@glennmglazer]

Came here to say point 1.

[@Cld136]

I work in semiconductor. This is the exact problem that we are facing with monolith software architecture. But because it is heavily dependent on legacy/old technologies, we have no choice but to continue using the same architecture. Thanks for an excellent video and quality contents.

[@chandanpatel6528]

Great teaching skill with awesome accent..keep it up buddy 👍

[@aashish01yash]

Advantages of Monolithic Applications 1) Network latency is not a factor in overall performance since its all one common codebase 2) Do not have to worry about ACID properties across different operations instead monolithic app will handle all as part of one service call 3) Each microservice could have different version available on endpoints and its orchestrator's responsibility to keep track of the version that they are using whereas in monolithic applications all modules are on one version

[@The_MONK_YT]

Scaling data layer is also possible in monolith using partioning,sharding, multi Az, read replica

[@shapelymum2364]

nice one

[@DileepGowda]

Can you create a playlist for all microservices related videos ? Its difficult to identify each video one after the other.

[@TechDummiesNarendraL]

There is a playlist :)

[@pgs4065]

are there blog version of these videos?

[@aashish01yash]

Hello I could think of few more disadvantages for monolithic applications: 1) Tightly Coupled Dependencies - All the different modules which are part of one codebase and could have dependencies or hard links between them preventing developers to cleanly maintain these modules 2) Upgrade Nightmare - For any upgrade in libraries for any of the module could have impact on other modules as well (I guess this can be considered as part of 1) 3) Release Heavy - What i mean by that is , if any module within the application goes a version upgrade then i have to release the whole application instead of that specific module 4) Difficult to Debug/ Cluttered Logs

[@TechDummiesNarendraL]

You got it right👌

[@glennmglazer]

One disadvantage of microservices is that if there is a large web of services calling each other on demand, there isn't a clear flow of control. This means that changing a service can have chaotic effects as the change ripples outwards to the callers.

[@badamtus6092]

Might sound like a dumb question, but why can we not use multiple different databases for a different modules within a monolith?

[@TechDummiesNarendraL]

You can, but monolith is not just about DB

[@badamtus6092]

Well, I agree. But you mention in 06:15, that scaling is a problem since all modules use the same database, causing a bottleneck. I also saw your comment of horizontally scaling DB also being a problem because of challenges in writing. But, assuming logical independency of modules, could we hypothetically keep separate databases and reduce bottlenecks?

[@badamtus6092]

Great content btw, thank you very much!

[@oyejohnson]

Why shade python (django) like that?

[@thenainasinghal]

Hi - One more important reason - if these is any problem in one portion of monolith then entire monolith will become down in production but in microservice, only that microservice will go down and rest all microservice will work properly in production.

[@TechDummiesNarendraL]

True and it depends on kind of problem too.

[@thenainasinghal]

@@TechDummiesNarendraL Yes, I agree. and because of deployment of microservices independently in different containers we have this added benefit. But definitely if other microservice depends on this microservice(defected one) then its work would be impacted.

[@thenainasinghal]

Hi.. Just noticed you have already covered this in next video. All your videos are really very good, informative and clear. It helped me a lot in many interviews. Thanks a lot for that. Really great open source work.

[@glennmglazer]

This depends a lot on how critical the microservice is. Consider an ecommerce website where the authentication service fails. Not letting people log in at all is almost certainly the right solution, otherwise people can impersonate each other.

[@dimahodan232]

I'm actually surprised that Mustang was established only in 1972. I thought this company was way older.

[@ghanshyam014]

Where do you work brother 😊??

[@shaileshhegde9205]

Definitely understanding, I have been part of monolithic architecture and they are a pain to understand!

[@priyeshshah3290]

I can think of couple of more disadvantages with monolith: No reusability: can’t extract code for a module and run it in another project. No common fixes: if two projects have duplicate modules, bugs needs to be fixed in both separately in both modules.

[@TechDummiesNarendraL]

Point👍

[@pvnarasimhareddy]

Voice is really low

[@amanbaranwal9535]

no one would mind if you speak normal english rather pushing hard on to get british accent. Its so irritating to listen.