While most of the world is still orbiting around clouds and Big Data, Micro Services are the latest obsession in tech circles. Although they sound new, Micro Services in some ways are like ‘going back to the start’ where codes were short, easy to deploy and change. At Captain Dash we believe in the disruptive ability of Micro Services. They are changing the way businesses build their architectures and in turn their teams.
As present architectures get stronger and heavier they are also becoming as slow and rigid as mammoths. A real burden in a world built on speed, agility and adaptability. To facilitate functionality in this environment developers are turning to the architectural approach of single, independent applications composed of small services. These applications are called Micro Services and they are connected through APIs. With Micro Services, complexity is achieved through connecting simple elements to each other in lieu of one heavy, complicated system.
Key points that define Micro Services:
- They have one, single function
- They are truly loosely coupled since they are physically independent
- Every single service can be written using any language or any tools given the independency
- They are product focused instead of project focused
- Centralised teams, which are responsible for the whole product cycle and decentralised data
- They are easier to test and fast to deploy for continuous delivery
- They are very easy to scale since only the pertinent parts need to be duplicated
So, does this mean that we need to rebuild our present architecture to keep up with Micro Services? No. Netflix and Amazon among others have pioneered the utilisation of Micro Services in conjunction with their pre-existing monolithic structures. Due to their flexibility Micro Services can be externally plugged to your monolith (a single, complicated, heavy architecture) for added benefits, much like little doses of Botox to the skin. And like Botox, Micro Services have a cost as well as need for superior knowhow.
But regardless of present complexities, the way forward with Micro Services is one that allows great flexibility and agility either by themselves or coupled with existing architectures.
Note: Captain Dash is starting a new series of posts on Micro Services. Some technical and some not so much. Our aim is to take this form of architecture that we use and make it simple to understand for everyone out there. These posts will go up every Sunday. So, follow us on twitter or subscribe to our blog and receive your weekly update on this fabulous architecture that is changing the way we do business!
Written By: Meghna Verma Meghna Verma is the Content Manager at Captain Dash. You can reach her on Twitter @M3GV3RMa .