The consolidation phase – steady migration to microservices

After the initial setup, other teams start working with the microservices approach. This expands the number of people dealing with containers and new deployments, so the initial team will need to give them support and training.

Training will be a critical part of the migration project—be sure to allocate enough time. While training events such as workshops and courses can be very useful to kickstart the process, constant support from experienced developers is invaluable. Appoint developers as a point of contact for questions, and tell them explicitly that their job is to ensure that they answer questions and help other developers. Make the supporting team meet up regularly to share concerns and improvements on the knowledge transfer.

Spreading knowledge is one of the main focuses in this phase, but there are another two: clarify and standardize the process and maintain an adequate pace of migrating the microservices.

Documenting standards will be helpful to give clarity and direction. Create checkpoints to make very explicit requirements across the board, so it's very clear when a microservice is ready for production. Create adequate channels for feedback, to be sure that the process can be improved.

During this time, the pace of migration can be increased because a lot of uncertainties and problems have already been ironed out; and because the development will be done in parallel. You should try to work on any new feature in a microservice way, though compromises may need to be taken. Be sure to keep the motivation and follow the plan.

本周热推：

Hands-On Docker for Microservices with Python 异构基因共表达网络的分析方法物联网服务平台技术 5G同频同时全双工技术 Learn Web Development with Python