The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started
Back to feedPost
Overview
TravelOS ERP is a high-concurrency fleet management and seat reservation engine engineered for intercity tour and transit operators to handle real-time dispatch, route synchronization, and instant ticketing.
The Problem
During peak booking windows and flash sales, simultaneous customer checkouts frequently triggered double-booking race conditions. Additionally, high database lock contention degraded dispatch dashboard performance and caused live manifest sync failures across remote driver terminals.
The Solution & Architecture
Distributed Concurrency Control: Implemented atomic seat reservation locks using Redis Mutex with strict TTL expiration, eliminating 100% of double-booking races under concurrent load.
Real-Time Passenger Manifest Sync: Architected bi-directional WebSocket pipelines to instantly synchronize seat statuses, passenger check-ins, and driver dispatch states with sub-35ms latency.
Relational Data Integrity: Designed normalized PostgreSQL schemas with Prisma ORM and multi-tenant isolation, ensuring seamless handling of routes, vehicle maintenance logs, and financial reconciliations.
Key Impact & Metrics
0% Double-Booking Incidents under 1,000+ simultaneous checkout requests.
< 35ms Lock Sync Latency across passenger and operator terminals.
100,000+ Manifest Records processed daily with sub-second query execution.
The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started
Related posts
Hi everyone, I’m Dani from Innsbruck, Austria.
I’m a senior full-stack developer and technical consultant with experience in C#/.NET, PHP/Laravel/Symfony, TypeScript/Angular, APIs, SQL, e-commerce and AI integrations.
I enjoy turning business requirements into reliable applications, integrations and practical AI-assisted workflows. I’m currently available for remote freelance collaborations and happy to connect with other builders, founders and teams here on Contra.
Nice to meet you!
contra.com
Danijel Bumbar’s Work | Contra
View Danijel Bumbar’s work on Contra. The Independent-first, commission-free freelance marketplace shaping the future of work.
Nice!
Your best-selling dish could be losing you money.
That insight shaped my dashboard work on DineIQ, a restaurant analytics competition project.
My challenge: turn complex analytics into clear, useful views. I approached it with focused Django dashboards, practical filters, and role-based access—helping managers explore their location’s menu performance and wastage together.
My role covered full-stack integration, UI/UX, dashboards, and architecture. Built with synthetic competition data, DineIQ illustrates why sales volume alone doesn’t tell the full story.
Better decisions start with better visibility.
#FullStackDevelopment #Django #DataAnalytics
A WhatsApp chatbot that automates tasks is NOT the same as a custom-built web application.
And honestly, I’ve noticed how much people love AI-powered WhatsApp bots lately.
As someone who develops AI workflows and custom websites, I personally believe that combining a well-built web application with AI puts you one step ahead.
Imagine having a custom interface, your own database, automated workflows, and an AI agent working together in one place.
That’s a completely different level of flexibility.
Don’t get me wrong: WhatsApp bots aren’t always the inferior option. They’re great for customer-facing interactions and quick communication.
But personally? I’d rather give customers a dedicated web experience whenever the project calls for it.
Are you Team WhatsApp Bot or Team Web Bot?
When the web app and the bot share one database, which side owns the conversation state: the n8n workflow or the app? That choice seems to decide whether a customer can switch between WhatsApp and the web view mid-request.