Dynamic Booking Pricing Engine — Model-Based Common Table Config
Model-based dynamic booking pricing engine deployed in 1 day for 5k+ daily bookings, reducing deployments by 90%.
Pricing updates no longer require code deploys.
Seamless high-volume transaction support.
Architected, built, tested, and shipped in 24h.
Hardcoded booking amounts required code changes and production deployments whenever marketing models or vehicle pricing rules changed.
Architected and deployed a dynamic booking pricing engine in 1 day, decoupling amounts into a centralized database configuration table to serve 5k+ daily bookings and reducing deployments by 90%.
Project description
Architected and deployed a dynamic booking pricing feature in a single business day, replacing hardcoded pricing constants with a common database table.
Engineered model-based pricing lookups that allow business teams to adjust vehicle booking amounts dynamically across marketing campaigns.
Serves 5,000+ daily booking requests with sub-millisecond lookup latency.
Reduced production deployment cycles by 90% by eliminating code releases for routine pricing updates.
Why I built this
Hardcoded booking values forced engineering teams to perform frequent production deployments whenever promotional pricing shifted.
Business stakeholders required real-time pricing flexibility across vehicle models and variants.
Process and execution
How the work moved
- Refactored hardcoded payment and booking amount logic into a flexible model-based table schema.
- Built dynamic lookup endpoints resolving vehicle model configurations and payment link amounts in real time.
- Delivered and shipped the entire feature to production within a single business day.
- Scaled the engine to process 5,000+ daily booking transactions with zero downtime.
What I owned
- Led the work as Associate Consultant - Java Backend Developer.
- Turned messy context into a clearer operating model, interaction direction, and rollout shape.
- Worked across stakeholders to move the project from framing into execution.
Notable decisions
Centralized configuration table
Replaced hardcoded vehicle pricing constants with a common configurable database table, slashing production deployment needs by 90%.
Rapid 1-day delivery
Streamlined schema migration and API handlers to design, test, and release the dynamic pricing engine in 24 hours.
What I learned from this
Centralizing configuration rules into normalized database tables decouples operational agility from code deployment cycles.
Rapid 1-day delivery is achievable with targeted architectural decoupling and clean schema design.