programturizmus.hu: From Legacy System to Kubernetes Microservices
programturizmus.hu is a leading digital platform in Hungary’s program tourism market. When growth and reliability demanded more, we migrated the legacy monolith to a modern microservices architecture running on Kubernetes — while keeping the service continuously available.
The challenge
The previous system had grown for years into a single large application covering bookings, content management, partner integrations, and administration. That made safe development, targeted scaling, and fast incident response increasingly difficult — especially during traffic peaks.
- Monolithic application: one failure could affect multiple features
- Awkward scaling: the whole system had to grow, not only the hot path
- Slower release cycle: frequent production deploys felt riskier
- Limited operational visibility: monitoring and fast response were harder
Our approach
We avoided a big-bang rewrite. Critical capabilities were extracted into dedicated services step by step, with the old and new systems running in parallel. That reduced risk and delivered measurable progress continuously.
1. Domain-driven decomposition
We mapped the business domains — bookings, content, partners, user accounts — and used them to define service boundaries. Each new service launched with a clear responsibility, API, and operational metrics.
2. Strangler Fig pattern
New services were built in front of and beside the existing system. Traffic was shifted gradually, and legacy components were retired only after the new path had proven itself.
3. Kubernetes as the operations foundation
Kubernetes became the target platform: declarative deploys, health checks, horizontal scaling, and environment separation (staging / production). Releases became more predictable, and rollbacks faster.
What we delivered
- Microservices architecture for the core business flows
- Kubernetes-backed operations with staging and production environments
- CI/CD pipeline for controlled, repeatable releases
- Observability: logging, metrics, and alerts on critical paths
- Near-zero downtime migration for end users
Results
After the migration, the platform scales where it matters, failures are more isolated, and the team can ship safe changes faster. programturizmus.hu is better prepared for traffic peaks and continued product development.
We did not just introduce new technology — we delivered more stable operations and a faster delivery rhythm for a growing platform.
Key technologies
- Kubernetes — container orchestration and scaling
- Microservices — domain-driven separation
- CI/CD — automated build, test, and deploy
- Observability — metrics, logs, alerts
- Incremental migration — Strangler Fig pattern
Facing a similar challenge?
If you want to move a legacy system to a modern Kubernetes-based architecture — without downtime — let’s talk.