Micro Services – The Dark side


We Never Promised You A Rose Garden

Micro Services work well because they reduce friction; they allow for flexibility and innovation.

They also increase risk!

One might argue that they are built for risk taking but that risk is worth nothing if the ROI is minuscule. The first problem is that Micro Services have a big upfront cost. Maintaining the cost of production for multiple services, testing, deploying and running them is no walk in the park.

Having a stellar team is the other caveat in order to succeed in Micro Services. All the engineers across the board need to be well versed in DevOps tools since these are very critical in the Micro Services environment. Alongside that the team needs to be comfortable with working on products versus projects. The responsibilities are multiplied.

When you break a structure into multiple little applications a lot of things become easier but the one thing that becomes complicated is the wiring and the interfaces that we need to attach to these components. If the process is not well thought out and designed backwards there can be all sorts of network latencies, lack of synchronization and contextual breakdowns.

Keeping it simple is the first rule of working with Micro Services. This form of architecture is complex enough without adding unnecessary frills to the elements. There is, with Micro Services, a danger of moving the complexity from inside the system to the outside. This is not good news since the complexity becomes harder to control and monitor.

All of these problems that Micro Services come with, though, can be mitigated with having a pragmatic approach towards a product. One can choose to start out as purely Micro Services based or to start out as a Monolith that is later refactored into Micro Services. At Captain Dash we love working with Micro Services and believe that they are the true data revolution. At the same time we make a conscious effort to never lose sight of the clients’ vision and end goal. The end goal of the client or the product is what ultimately matters.

To stay updated with our series on Micro Services architecture follow us on twitter or subscribe to our blog.

Written By: Meghna Verma Meghna Verma is the Content Manager at Captain Dash.  You can reach her on Twitter @M3GV3RMa .