Nostr Web Client

No unfortunately I don’t have data I can share, but on big market platforms the clients want to know market liquidity every 5ms. High Frequency Trading demands information about the liquidity (not transactions) of every consolidated limited order book (every ticker) at a ferocious rate, in order to execute arbitrage.

Every HFT client wants every limit order of every ticker available on every trading terminal, every 5ms. People pay a lot of money for these feeds and the feeds are all built on websockets.

Pro Tip: clients don’t poll the exchange. The solution to the traffic and scalability problem lies in the choice of database framework.

Financial markets are orders of magnitude more traffic than all of social media, equivalent to millions of Tweets/second. These are the people renting all the antenna slots at data centres and dropping $20m on superconducting lasers to get insane bandwidth at insane latency.

I might be able to dig something up to share next week.

Melvin Carvalho 3y ago

Got it. Im still unsure it compares to the whole REST surface

A friend of mine does market monitoring for the biggest exchange in europe. It's a few terabytes a month

Archive.org which is one site has 10,000 terabytes

REST has a proven track record to scale to billions of people with low resource intensity. Websockets are a newer technology, let's see how they get on.

What's interesting is most older web systems started with HTTP then added websockets for realtime. Nostr starts with realtime, and we can explore how to scale that with supporting NIPS.

Fun times! :)

Reply to this note

Please Login to reply.

Discussion

⚡️🌱🌙 3y ago

The exchange is a few terabytes a month, because it is architected correctly.

You don’t have every user constantly polling the entire exchange for a refresh, that simply doesn’t scale. Instead they broadcast change to clients.

It’s a feed, not a query. Again the solution is the choice of DB engine. Does that make sense?