Reply to thread

Message: <blockquote data-quote="NEMISIS" data-source="post: 29486344" data-attributes="member: 494668">primary deciding factor is scalability, and there are lot of other factors like budgets etc.for small scale application, if you have a few dozen shops and a few thousands customers, monolithic app would work, mostly a single code base. but lot of problems arise when you want to scale up. you can't scale up single service, you have to scale up the whole thing. there are some strategies you can use to scale up monolithic systems but running cost can be high, and maintainability is  low, there are other problems like single point of failures etc. If you are building an application for a business in sri lanka, 70-80% of the time, you would be able get away with a monolithic application.Micro service architecture is highly scalable. you have granular level control when scaling.  In the real world there will be some services called more often than others, and there will be some services that are rarely used. If you break these in to multiple micro service, you can simply scale up one service as we need it.For an example, site like Daraz/Amazon, there will be lot of requests for "Search" and relatively low number of requests for "View profile",  if you have micro services, you can simply scale up the Search and View Profile services differently. you can't do that if you have a monolithic application which both services are in a single deployment.You have to carefully decide based on scalability/expected number of users etc. for a small business with few branches/shops, monolithic application can be be a better option.Both options has its own pros and cons.</blockquote>

Verification: Winadiyakata thappara keeyak tibeda?

Top Bottom