This case study is still being written. Full details are coming soon.
Backend / APIArchived
Amala: Java Microservices on Kubernetes
APIs built as Java microservices and deployed to Kubernetes.
2019-amala-project · main
# Enterprise Integration
$ java -X POST /2019-amala-project/v1/sync
→ 201 Created
{ "status": "ok" }
publish 2019-amala-project.synced
- Role
- Integration Engineer
- Timeline
- 2019
- Domain
- Enterprise Integration
- Stack
- 2 tech
- Status
- Archived
01
Overview
Built APIs for the Amala project as Java microservices deployed to Kubernetes.
02
Problem & Solution
Problem
The Amala project needed APIs that could be deployed and scaled as services.
Solution
Built the APIs as Java microservices and deployed them to Kubernetes.
03
Workflow
Three actors interact with the service; the diagrams are written in English to stay consistent across both languages.
flowchart diagram
04
Tech Stack
language
Java
infrastructure
Kubernetes
Chaos Engineering — Resilience Game Days
Prepared and ran a chaos engineering game day for the merchant-promotion service — dependency fault injection with toxiproxy across staging and production, keeping success rate near 99% with MTTA 1m / MTTR 12m, and turning one non-standardized error message into a cross-team follow-up with product and UI/UX.
Service Decommissioning & Cost Optimization — Fetcher/Ingestor Sunset
Safely sunset two unused merchant-promotion backend services and an unused Redis cache instance, moved remaining responsibilities to the aggregator service, and refactored the main binary to Clean Architecture — delivering a meaningful monthly and yearly infrastructure cost reduction and a cleaner, more maintainable codebase.
Graceful Handling for External Calls — Dependency Resilience
Implemented graceful handling — timeouts, fallbacks, and graceful degradation — for every external call the merchant-promotion service depends on, and rolled out a Redis caching layer across repo functions that grew coverage from 97 to 195 functions, reducing external RPS cost and keeping the service healthy when dependencies degrade.
Interested in working together?
Order, payment, or high-traffic event pipelines — let's talk architecture and trade-offs.