In software industry it is always hard to know what you are building untill some time, even then, good luck knowing what you are building. So Monolith vs microservice is wrong comparisone in my opinion. It is easy to start with the monolith if you do not know your problem well, or the solution, and you are trying to descover the domain. The observability will be great, you will able to move logic from a module to another and may never end up needing a microservice at all. But when you have a clear idea about the domain and your organization, and you started to need separation, then you start thinking of splitting your monolith. And there are many ways and strategies that can help during that jurney. Untill then good luck
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
In software industry it is always hard to know what you are building untill some time, even then, good luck knowing what you are building. So Monolith vs microservice is wrong comparisone in my opinion. It is easy to start with the monolith if you do not know your problem well, or the solution, and you are trying to descover the domain. The observability will be great, you will able to move logic from a module to another and may never end up needing a microservice at all. But when you have a clear idea about the domain and your organization, and you started to need separation, then you start thinking of splitting your monolith. And there are many ways and strategies that can help during that jurney. Untill then good luck