Skip to content
Theme
OnDevice Tools

SoftwareCloud & Services

DynaPORT modernization moves to Google Cloud with AlloyDB

The DynaPORT modernization will use AlloyDB for PostgreSQL and Google Kubernetes Engine. The migration aims to move a port operating system away from legacy database logic.

Illustration of a port container crane with a Google Cloud data centre behind it

Key takeaways

  • DynaPORT modernization will move to Google Cloud using AlloyDB for PostgreSQL and GKE.
  • The migration includes over 1.2 million lines of code and Oracle PL/SQL to PostgreSQL PL/pgSQL.
  • Tata Consultancy Services and a port operator are involved in the project.
In this article
  1. What changed
  2. Important details
  3. Who is affected
  4. What it means

What changed

Illustration: cloud, Google logo, Google Cloud logo, Kubernetes logo and the labels Alloydb for PostgreSQL, Dynaport, Gemini

Google Cloud Blog reported on 20 November 2026 that the DynaPORT modernization is moving to Google Cloud. The project involves Tata Consultancy Services and a port operator. The port operator has used DynaPORT for more than two decades. The plan is to move the Terminal Operating System to AlloyDB for PostgreSQL and Google Kubernetes Engine.

The change is a move from a legacy on-premises architecture to a cloud-based one. DynaPORT is a next-generation Terminal Operating System. It was developed by Tata Consultancy Services. The new design uses AlloyDB for PostgreSQL and Google Kubernetes Engine.

The migration is part of a cloud modernisation journey. The old system used monolithic application servers. The new design uses containerised microservices. The microservices will run on Google Kubernetes Engine.

The target architecture follows the Google Cloud Architecture Framework. It transforms the old middleware. The goal is to support fast enterprise changes. The plan uses AlloyDB and GKE.

Important details

The legacy DynaPORT Cargo module had a complex database design. Its database held many packages. The packages contained over 1.2 million lines of code. The database also had stored procedures, functions, and triggers.

Critical business operations were handled inside the database. The new system will use PostgreSQL PL/pgSQL. Google Cloud Database Migration Service was used. The team used Gemini-assisted AI code help.

The old design was built for fast database round trips. The new design keeps logic in the database engine. AlloyDB provides accelerated storage and compute. The case study notes a performance spike in batch invoice generation.

Such a spike could affect real-time operations. The migration also involved converting Oracle PL/SQL to PostgreSQL PL/pgSQL. The evaluation compared two strategies. One strategy was to move logic to application services.

The other was to keep procedural logic in the database. The team chose the second approach. The decision was based on timeline and risk.

The migration used Google Cloud Database Migration Service. Its conversion workspaces helped with bulk transformations. The team also used Gemini-assisted AI code refactoring. The remaining code needed targeted engineering work.

Who is affected

The customer is one of India's largest commercial port developers and operators. Its cargo terminals have used DynaPORT for more than two decades. The system supports bulk, break-bulk, and liquid cargo. It also supports containers and general cargo.

The migration may affect these port operations. The project may affect how ports plan and automate cargo. The system supports planning, automation, and orchestration. It covers order-to-invoice processes.

It supports vessel, rail, truck, and barge operations. The modernization may affect these areas. The customer has relied on DynaPORT for over two decades. The project is a landmark milestone for the customer and TCS.

The system acts as a key control point for port operations. It manages planning, automation, and orchestration. It covers the order-to-invoice lifecycle. It supports multimodal cargo.

What it means

The project aims to remove technical debt. It also aims to improve operational visibility. The old design made releases difficult. It required manual deployment runs.

It had high regression risk. The new architecture may support faster delivery. The migration is still a case study. It offers a path from legacy systems to cloud native services.

The shift may change how the port handles data. It may change how the port handles operations. The use of AlloyDB and GKE is central to the plan. The final outcome is not yet known.

The case study describes a systematic deconstruction of legacy technical debt. It also describes a strategic rationale for AlloyDB. The project may offer a model for other logistics systems. The customer and TCS are central to the plan.

Sources

  1. DynaPORT modernization on Google Cloud with AlloyDB for PostgreSQL and GKEGoogle Cloud Blog

Tags

Spotted a mistake? See our corrections policy. Read how News by OnDevice works in our editorial policy.