Until recently it has been entirely regular for one to choose the best available language at the given time. Due to the centralized governance of the Monolithic architecture we tend to standardize on single technology platforms. To best be able to take advantage of the merits of a chosen language it is common to overlook or compromise with its shortcomings.
Over time developers have given in to the temptation to look for that one golden language that works, that one language that has the ability to do everything. Up until now such a language has not been created.
With the coming of age of Micro Services we realized that maybe the answer does not lie in a golden language because not every problem needs to be solved in that one language. Why not use the best possible solution for a given problem instead of trying to make the same solution fit every problem.
Due to the decentralized and de coupled nature of Micro Services we have the option of doing just that. To look at a given challenge and solve it using the best possible language we can. Of course this does not mean that we have to use different languages for everything, just that we have the option to.
The de coupling between individual services is what helps the architecture to communicate and work seamlessly despite there being multiple languages at play in the system. To put a layman’s twist into this let’s say that Micro Services are a Google translate that actually works! Imagine being able to express yourself profoundly in any language of the world without the fear of something being lost in translation.
Profiting off of this wonderful polyglot ability of Micro Services allows us to innovate faster since challenges can be addressed quicker and with more efficiency. Hence, a tower of Babel it might be but the communication is definitely not hindered!
Written By: Meghna Verma Meghna Verma is the CMO at Captain Dash. You can reach her on Twitter @M3GV3RMa .