2 ms·
Not quite. With a monothlic, it's an overhead to migrate data, because one small mistake will take your application down. So, in real world, it takes more over
by revskill 8y ago
Not quite. With a monothlic, it's an overhead to migrate data, because one small mistake will take your application down.
So, in real world, it takes more overhead to manage a monothlic than a microservice architecture.
- iBelieve 8y agoWith microservices, if you make a mistake and take part of your application down, aren't you worse off because only part of your application is running and is now in an undefined state?
- revskill 8y agoIt's fine to have only one part of the application down, instead of the whole go down. Each part of application is ran by different roles/functionalities.
- threeseed 8y agoYou really need to think that comment through first. If you're a bank then it's fine if your notification microservice goes down because at least you can still accept payments, handle deposits, transfer money etc. In almost no situation is there a case where having no availability is preferred over partial availability.