This past year we have witnessed how many companies have successfully integrated Micro Services into their architecture. In fact, 2015 has been touted as the year for Micro Services.
It is all very fine for certain visionaries in an organization to push for Micro Services adoption from a strategic point of view but it is often found to be difficult to get people on board. Now, if it is indeed that great of an idea then why is it so difficult to convince teams to adopt them?

The answer is very simple – Turf!

Mostly the data in organizations exists in silos and is utilized as such. The problem that Micro Services present to such a way of functioning is that they represent a different way of doing things where managers often have to loosen their hold on their data. Thus, turf wars come into play.

There are some measures that can be taken to make a smooth transition in such a case:

Start by creating Micro Services for new application features to begin with. As development progresses work on refining and making changes where they need to be made.

To begin with keep the teams working on Micro Services separate from the team working on the monolithic architecture.

Provide the time and support to various teams to explore how Micro Services work and incorporate them into their work process.

As the Micro Services structure progresses encourage the teams to intermingle, have exchanges and facilitate cross training of skill sets.

As the skill differences become smaller and the comfort level of various teams increases start the breakdown of silos – both in terms of teams and data utilization.

As the Micro Services architecture expands start sliding slowly from the monolith to micro services.

Create standardized templates for development to make the creation of Micro Services easier.

As the architecture and the culture it brings get accepted across the organization start pruning the older Micro Services and replacing them with finer, more current ones.

While, it may be difficult to get everyone in an organization on board with Micro Services it is well worth a try as it can not only create better, more scalable software it can also help build better team dynamics.