2025client work

EasyBooking

I put service discovery config and packaging firstA scalable system is set up before feature fun starts

problem

The challenge: keeping a distributed hotel booking platform clean as it scales multiple services and features

I use configs and tools that prevent future headaches and broken builds

Package Kubernetes releases with Helm rather than hand-crafted YAML one at a time.
tradeoffMore templating complexity per chart.
outcomeEvery microservice release is reproducible from one chart rather than drifted manifests.
Centralize OAuth and config in their own services.
tradeoffTwo extra deploy units plus a runtime dependency between gateway identity.
outcomeA new microservice doesn't reimplement auth or config. Its responsibility stays its service domain.
Measure each service's Sonar quality gate in CI.
tradeoffSlower CI on every commit.
outcomeCoverage and code-smell regressions are blocked before merging, not detected in code review.