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
The hardest part of a booking app isn't the booking.
It's what happens when two people tap the same slot four milliseconds apart.
The obvious approach is to check whether the slot is free, and if it is, book it. That works perfectly in testing, because in testing there's one of you. In production, both requests run the check before either one writes. Both are told yes. Both book. Now you have two teams turning up at the same turf, and a venue owner who no longer trusts your app.
The instinct is to fix this in the application — a flag, a check, maybe a mutex. That's fighting the problem in the wrong place. Your app might be running on four servers; they can't see each other's decisions.
The fix is to stop asking permission and let the database refuse:
A unique constraint on (venue, slot). The second insert fails. Not "usually fails" — it cannot succeed, by definition.
A conditional write. update slots set booked_by = ? where id = ? and status = 'free'. If it changes zero rows, someone beat you. That's your answer.
A short-lived lock while they're paying. Hold the slot for five minutes in Redis, release it if they abandon checkout. This is the one users actually notice, because nothing is worse than paying for a slot that was gone before you finished typing your card number.
None of this is exotic. But it only shows up when two people want the same thing at the same time, which is exactly the moment your app is finally working.
Anyone else been bitten by this one? I've seen it in booking, ticketing and inventory — same bug wearing different clothes each time.
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
Trending
retrofuturism
Share your favorite designs from the past exploring the distant future. Or your own take on the aesthetic 🚀
halftone
Dots. Texture. Grain. Let's see your designs using the halftone technique.
Midjourney
Creatives are showing off what they're making with Midjourney.
colorgrade
Video editors sound off: How do you enhance the mood of your video in color grading?
Related posts
MOST HOTELS DON’T HAVE A BOOKING PROBLEM.
THEY HAVE A BROKEN DIGITAL GUEST JOURNEY.
A guest discovers your hotel.
They search for you.
Then the friction starts.
🌐 The website doesn’t answer enough questions.
📞 They call to confirm availability.
💬 They move to WhatsApp to book.
💳 Payment becomes another process.
🚕 Airport pickup requires another conversation.
Eventually, they choose the easiest option:
A third-party booking platform.
The hotel may still get the booking.
But it has lost control of the customer relationship.
While working on the digital transformation of ORANTO, this became one of our biggest insights:
⚡ A HOTEL WEBSITE SHOULD NOT BE A DIGITAL BROCHURE.
IT SHOULD BE PART OF THE HOTEL’S REVENUE INFRASTRUCTURE.
Instead of asking:
“Do we have a good website?”
Ask:
❓ HOW MUCH OF THE GUEST JOURNEY CAN HAPPEN WITHOUT STAFF INTERVENTION?
Discovery → Room selection → Availability → Payment → Confirmation → Airport pickup → Guest services.
Each unnecessary call, message or manual handoff creates friction.
And the opportunity doesn't stop at checkout.
If the hotel owns the relationship, guest history can help drive better service, smarter follow-ups and repeat bookings.
That’s the bigger opportunity we explored with ORANTO:
Not simply redesigning a hotel website.
But connecting the digital guest journey from discovery to return.
Hotels spend heavily creating incredible physical experiences.
But your guest often experiences your hotel digitally before they ever walk through the door.
If that experience is broken, part of your hospitality experience is broken too.
Check out the full case study here
Want to build one for your business? Book a session with me
This is really nice and attractive
Weighting gestures to match real-world friction is peak UX design. Turning an exit action into a deliberate signature adds incredible weight to the product experience
Datonix is a clean database monitoring dashboard designed to help teams track branch health, compute usage, server uptime, connection performance, queries, and productivity activity in one organized SaaS interface. With a dark sidebar, light dashboard layout, purple accent colors, real-time monitoring charts, branch status lists, performance cards, and heatmap-style productivity tracking, the design makes complex database operations feel easier to scan, manage, and act on.
📩 Collaborate with Us? Contra Cansaas Agency
