Solo building the backend restaurants actually need — no team, 6 months in

Most intros start with a bio.

Mine starts with a bug I never wanted to see in production: two couriers claiming the same order at almost the same time.

I’m Anna, a solo developer from Yerevan, Armenia.

I’ve been building Restaurant OS on the side while working as a Frontend Lead on a real estate platform.

Building it taught me that the hard part is rarely CRUD.

It’s what happens when reality gets messy: two people update the same order, a courier loses connection mid-delivery, or the kitchen runs out of an ingredient during preparation.

So I focused on making state changes safe and visible — conflicting updates can’t silently overwrite each other, roles have different permissions, and the kitchen, delivery, and admin dashboards stay in sync in real time.

I’m curious how others have handled real-time state conflicts in production: optimistic locking, queues, event sourcing, or something else?

Happy to meet other makers building systems where “almost at the same time” is a real product problem.