The brief

Build a working cryptocurrency exchange — not a prototype. Real-time market data, transaction flows that hold up under scrutiny, and a REST API back end that serves web and mobile from one contract.

Why exchanges are unforgiving

Prices move constantly, so the data path has to be genuinely real-time rather than polled-and-hoped — a price that is three seconds stale is not a price, it is a liability. Money movement has to be correct under concurrency: a race condition in a trading flow is not a bug you patch next sprint, it is a loss. And one API has to serve web and mobile without quietly forking into two back ends that drift apart.

Those three constraints drive nearly every architectural decision on a project like this — and getting them wrong is expensive in a way most web work is not.

The result

coinswift.exchange runs in production, handling real-time trading flows, with one REST API back end serving both web and mobile clients.