Microservices Platform Migration: 6-Months Implementation

Grid Dynamics Holdings, Inc.

Learn about the importance of Microservices Platform, our best practices and solutions, and get it implemented and customized for your own Azure cloud presence.

The GD team accumulated a lot of experience building cloud presence for its customers and distilled that knowledge into a blueprint for a microservices platform.

The platform is a generic implementation which addresses the majority of questions arising when companies encounter the world of cloud and microservices for the first time. The platform is capable of hosting various workloads when deployed, without spending time on the “plumbing” work usually associated with the beginning of a cloud journey. This allows companies to focus on their business domain logic and enables quick onboarding of “clean slate” implementations as well as the easy migration of existing technical solutions from other cloud and on-premise systems to Azure.

The reference microservices platform supports multi-tenancy and high availability / disaster recovery scenarios and can be scaled on-demand. It leverages the IaaC approach, which helps with reducing operational costs and provides a unified infrastructure for all stages of development.

Grid Dynamics will host a workshop which will cover the basic concepts of what a microservices platform is and why it’s needed, as well as architecture for the reference implementation and various components of the platform, the ideas of modularity and possibilities of customizations, followed by open discussion focusing on the Customer’s specific requirements and how the solution can be integrated into an existing technical roadmap.

As a next step, the instance of the microservices platform will be built in the Azure subscription provided by the customer, which will incorporate customizations identified during workshop/discovery phases, and the first set of pre-identified applications deployed and handed over along with the trainings required to maintain and extend the platform if needed.

The next steps may vary depending on the types of workloads or specific needs, but usually include continuation of onboarding for the applications combined with further enhancements and productionalization.