4 ms·
Postgres has its advantages, but for message queues I’d stick with SQS. I built out a trading firm last year that was basically Postgres, some dotnet services a
by rc2026 3mo ago
Postgres has its advantages, but for message queues I’d stick with SQS. I built out a trading firm last year that was basically Postgres, some dotnet services and SQS queues and we got acquired for $140M. You can build some fairly formidable systems if you keep them simple.
- f3408fh 3mo agoSounds interesting. Can you elaborate? You got acquired one year into doing business for 100M+? Impressive
- rc2026 3mo agoSorry, that's not entirely accurate - we started in 2024 and were acquired in 2025, so it was just under two years.
- Imustaskforhelp 3mo agoAs @f3408fh has said, I am also curious to knowing more about it if possible. I had always thought that trading firms might be some of the sole exceptions of over-engineering as I had went into the rabbit-holes of FPGA's and found that some of the use-cases of that technology was trading firms using it to literally shave off even a few milliseconds and so the amount of optimization there So I am a bit curious how postgres/some dotnet services and SQS queues is able to create a trading firm and scale it and even sell it for 140M$. It feels like my understanding of the situation was a bit uncertain then but could you please elaborate more if possible?
- rc2026 3mo agoI'm generalizing a bit, we built a trade-surveillance system that integrates with various trading terminals.