According to a Hindi saying, “Necessity is the mother of invention.” As your products or services grow over the period of time, you may start feeling the need for microservices. I do not suggest developing your product using microservices from day one. It depends on your product requirements whether you should choose a microservices-based architecture or a monolithic one.
In a recent discussion with a CTO, he asked whether he should go with a microservices-based architecture or a monolithic one.
I asked him two questions:
- Are your product requirements clear, or are there chances that they might change?
He said, “Yes, the product requirements are not clear yet and might change.”
Then I asked my second question:
- Do you have enough resources to manage a microservices-based architecture?
Again, his reply was, “No, I don’t have enough capable resources to manage or handle the architecture. I need to hire the required resources.”
After hearing his answers, I said, “I think you should not go with a microservices-based architecture. Instead, it would be better to go with a monolithic approach.”
You can’t blindly choose a microservices-based architecture. If your product requirements are very clear, or you have been running the product offline for a long time and have a sufficient customer base, and you want to develop a fresh product in this scenario, you should go with a microservices-based architecture. Here, you don’t need to rely on hit-and-trial methods. You already have a large customer base and need a scalable product for your organization or company.
Developing a monolithic application is not a big deal. You can use any resources to build a monolithic architecture-based application. But for a microservices-based architecture, you need skilled resources with the skill sets like AWS/GCP/Azure, Docker, Kubernetes, Ansible, and Grafana.
Are you confused?
If you are unsure whether to go with a microservices or monolithic approach, I can help you.
Just book a FREE discovery call with me or DM me.