AWSKanniah Vagathupatti JaikumarProblem & solution
Datalex, a leader in airline ecommerce, needed to modernize its mature EJB2/Java 8 system for Modern Airline Retailing while maintaining continuous airline operations. Over three days, 16 Datalex engineers and 6 AWS specialists proved migration feasibility by extracting a Reservation service into a Spring Boot microservice on Java 21. The team used agentic AI tools—Kiro and AWS Transform Custom—to automate code changes, and established repeatable patterns for DevSecOps, observability, and a multi-agent AI prototype via Amazon Bedrock AgentCore. A business service proxy using the Strangler Fig pattern enabled incremental migration with backward compatibility. The board approved significant investment, the prototype team expanded into a full Agile team, and the EBA shortened discovery from an estimated 8–12 weeks to three days.
Datalex is a leader in airline ecommerce solutions, with a 20+ year old EJB2/Java 8 system that powers shopping, pricing, and booking for major airlines. The industry is moving to Modern Airline Retailing (offers-and-orders model with AI-native experiences). Datalex needed to evolve its system to this future without disrupting current operations. The CTO sponsored Project Phoenix, a modernization roadmap, but needed to prove feasibility. In December 2025, partnered with AWS for a 3-day Experience-Based Acceleration (EBA) workshop to accelerate the migration.
AWS Experience-Based Acceleration (EBA) workshop with four parallel workstreams: microservice prototyping (extracting Reservation to Spring Boot/Java 21), DevSecOps CI/CD pipeline (Amazon ECS, ECR, Security Hub), QA and observability (CloudWatch, Datadog, Strangler Fig gateway), and agentic AI proof of concept (Amazon Bedrock AgentCore with authentication, data retrieval, reporting agents). Used AI tools Kiro and AWS Transform Custom to automate code changes. The business service proxy routes between old and new systems for incremental migration.
Migration from EJB/Java 8 to Spring Boot/Java 21 was proven feasible in a three-day EBA workshop, establishing reusable patterns for the remaining codebase.
A business service proxy using the Strangler Fig pattern allows incremental migration without big-bang cutover, with backward compatibility via Kong API Gateway.
The EBA methodology shortened discovery from 8-12 weeks to three days and provided working code and measurable results that secured board investment.
They used a Strangler Fig pattern with a business service proxy that routes traffic between existing and new microservices, allowing incremental migration. The proxy can switch via a simple parameter change, enabling non-regression testing and real-time validation.
Agentic AI tools like Kiro and AWS Transform Custom automated code changes. For the AI proof of concept, Amazon Bedrock AgentCore coordinated specialized agents for authentication, data retrieval, and reporting, integrated with Kong API Gateway and secured via Amazon Cognito.
The board approved significant investment, the prototype team expanded into a full Agile team, and the company established repeatable migration patterns. The EBA shortened the discovery phase from an estimated 8-12 weeks to three days.
Summaries are generated from the original by a language model. Check the original before relying on it.
See the idea
Amazon EVS runs VMware Cloud Foundation on AWS bare metal, so the design question becomes where each workload's data lives. This layered diagram shows how vSAN, FSx for ONTAP, and cross-Region DR divide the work.
Keep reading
The Good Stuff
Paid picks we use ourselves. Links carry a referral code — a subscription through one earns us a commission at no extra cost to you.
One useful email. Unsubscribe anytime.
