Cloud Transformation

Modernisation Factory on Alibaba Cloud

A strangler approach: API Gateway moves routes one by one from the legacy application to microservices on ACK.

From the Cloud Modernisation Factory in the Alibaba Cloud offering, a factory and strangler approach. API Gateway sends each route to a new service on ACK once it is ready, with Microservices Engine and Service Mesh around the services; Data Transmission Service keeps the databases in sync until the old code can retire. Every service comes off the same pipeline and templates.

moved routesremaining routessynceventsown schemadeployUsersLegacy estate · shrinkingAlibaba CloudEdgeNew services · microservices on ACKFactory toolingUsersLegacy applicationmonolithLegacy databaseWAFAPI Gatewaystrangler routingACKone cluster per environmentService Afirst sliceService BService Cnext waveMicroservices Engine(MSE)registry and configService Mesh (ASM)mTLS, traffic shiftingApsaraMQeventsData TransmissionServicekeeps data in syncPolarDB forPostgreSQLApsara DevOps Flowone pipeline templateContainer Registry(ACR)Terraformor ROS templatesARMSold and new path compared

Point at a component to light its links; select it for what it does here and the practice that makes it right on Alibaba Cloud.

When to use it

  • A large legacy application that cannot be rewritten in one go
  • Users who must not notice which part has moved
  • Many applications to modernise, worth a repeatable factory

How NGT delivers it

Built from code, reviewed at a gate by an NGT architect, and handed over with runbooks your team can run.

Cloud Transformation