Member-only story
Enhance and polish your Monolith before switching to Microservices
Crying out Cloud
Introduction
Even though our industry is evolving rapidly, we always have some sort of legacy applications or existing code bases that should be maintained and enhanced. Companies are not supposed to switch to the latest and greatest and rewrite their entire platform. However, there comes a time where you all agree unanimously that you want to update and switch to something new. Let’s see how
Your team is spending most of his time maintaining the code rather and adding features. Also, users are management are complaining about some speed and performance issues. In your mind, you’re just a useless lead that can’t neither ship new features to production nor protect your team from your slow buggy application.
Then and surprisingly, an article popped up in your feed showing the popularity of a Microservices architecture. You see that as the new trend that can be applied to solve all your problems!
Just like Lyon King, you present your godly solution and to the team pitching how it will change their life:
Performance won’t be an issue, no big and chunky code, feature oriented deployments… you name it! Everyone is on board.
