Transport Management System: 7 Microservices Platform with AWS Cloud Map Service Discovery
Built TMS logistics platform with 7 Spring Boot microservices on ECS Fargate using AWS Cloud Map for internal DNS discovery, RDS MySQL, and multi-environment CloudFormation stacks.
Results: 7 Microservices
Gateway, Fleet, Load, Asset, User, Notification, Discovery
AWS Cloud Map for internal DNS
Identical dev and production setups
All services use DNS discovery
Why This Matters
“AWS Cloud Map simplified our service communication dramatically. Services find each other via DNS names like fleet-api.local without any hardcoding. Adding new services is straightforward - they just register with Cloud Map and are discoverable.”
These results demonstrate the tangible business value of investing in the right technology infrastructure — from improved reliability to measurable cost savings.
TMS Logistics's Challenge
TMS Logistics was building a next-generation transport management system to compete with legacy TMS providers. Their platform needed to orchestrate fleet tracking, load management, asset monitoring, and customer notifications — all through a unified API gateway.
Technical challenges:
- Seven microservices (Gateway, Fleet, Load, Asset, User, Notification, Discovery) needed dynamic service-to-service communication
- Hardcoded IP addresses created deployment friction and prevented elastic scaling of individual services
- Central RDS database needed secure, connection-pooled access from all services without credential sprawl
- Development and production environments had manual configuration differences causing deployment failures
- Spring Cloud services required Eureka-style service discovery without managing a dedicated discovery server
Our AWS ECS Fargate Solution
We designed a complete microservices platform using AWS Cloud Map for native service discovery, eliminating the need for hardcoded endpoints or self-managed service registries.
AWS Cloud Map Service Discovery
Implemented AWS Cloud Map with a private DNS namespace (*.tms.local) enabling services to discover each other using simple DNS names like fleet-service.tms.local. ECS automatically registers and deregisters service instances as tasks start and stop.
Implementation Details
API Gateway Architecture
- Central API Gateway service routing external requests to internal microservices
- Path-based routing directing /fleet/* to Fleet Service, /loads/* to Load Service, etc.
- Centralized authentication and rate limiting at the gateway level
Database & Infrastructure
- RDS MySQL with connection pooling configured per-service for optimal database utilization
- Secrets Manager integration for secure credential injection without environment variable exposure
- Modular CloudFormation with separate stacks for infrastructure, each ECS service, and shared resources
GitHub Actions pipelines deploy each service independently, with automatic Cloud Map registration ensuring zero-downtime deployments.
Technologies Used
“AWS Cloud Map simplified our service communication dramatically. Services find each other via DNS names like fleet-api.local without any hardcoding. Adding new services is straightforward - they just register with Cloud Map and are discoverable.”
Related Content
Infrastructure as Code Consulting
Learn about our infrastructure as code consulting expertise and how we help companies like TMS Logistics.
Explore serviceEnterprise CRM Platform: Multi-AZ ECS Fargate Deployment with Zero EC2 Management
CRMified
School Nutrition Platform: 6 Microservices with Grafana Loki Observability and Auto-Scaling for Peak Lunch Hours
MealManage
Travel Platform Microservices: 4-Service ECS Architecture with Grafana Loki Centralized Logging
BPL Travel Platform
Ready to achieve similar results?
Let's discuss how we can help transform your business with the right technology solutions.