So, the real question is should you be adopting a Micro Services architecture? The straight answer to that is, YES! Adopting yes. Changing your entire system from Monolithic to Micro Services, maybe not.
In the past few weeks we have propounded the various advantages Micro Services has to offer you and your business. But, let’s be real. Changing an existing architecture is not only a time consuming and logistically difficult thing to do but also immensely expensive. Much like getting an entire face job done to smooth away wrinkles.
So, what is the solution?
Recently the strongest advocates of Micro Services seem to suggest that there are only two options – either you work with them or risk becoming obsolete. Two very extreme choices of architectures, which seem to come with an ‘either-or’ label. But, there does exist a middle path that few seem to be talking about - starting with an existing monolith and adding on an exoskeleton of Micro Services APIs.
At Captain Dash, most of our clients have Monolithic Architectures while we work using Micro Services APIs. We neither touch nor change in anyway the existing architecture of our clients. Instead we work by injecting doses of Micro Services APIs as and when needed for us to make the entire system more agile and modular. I would like to say that this is like injecting small doses of Botox into you skin as and when needed to keep wrinkles at bay instead of opting for an all out plastic surgery.
We have found this method of marrying the two architectures works very well for us in terms of giving us all the advantages of Micro Services and keeping the costs and overheads to the minimal.
So, if you work with an existing Monolithic Architecture and have been spending many a sleepless moment wondering if your architecture is truly becoming obsolete and dying out, then, Micro Services could just be the Botox that your system needs!
Written By: Meghna Verma Meghna Verma is the Content Manager at Captain Dash. You can reach her on Twitter @M3GV3RMa .