undefined

points

[-]

Thank you! I spent a decent chunk of time designing PicoMQ, so the documentation had a natural progression.

Exactly, streams can essentially be rooms, and since the ordering is preserved, a Discord-like application is a strong use case. I’m even considering building one using PicoMQ as an example showcase.

The pricing is going to be dirt cheap, and the best part is how easy it is to scale up vertically or add nodes. For some raw numbers, assuming 1M messages/day, 200B per message, ~6GB/month, all-inclusive, it would be $30 to $150 a month, and storage would be the cheapest part.

by soleveloper1 hours ago|

parent|

[-]

Yes, discord as an example would be awesome, exactly what I thought.

Is this back of envelope pricing include the traffic/bandwidth of the readers?

That could easily be 10-100x of number of messages.

This solution together with a cheap/free caching layer (especially for non members/writers) could be amazing.

BTW, a classic example would be an hn mirror. ;)

by adesh_nalpet1 hours ago|

parent|

[-]

Yeah, much of the base cost I mentioned was from the compute, networking and S3 write costs, which could sustain a lot more messages for sure. It also depends on the number of active streams/rooms, the throughput bursts, as opposed to a steady state.

But as we speak, I am in the process of running open-benchmarks on AWS with cost attribution. I'll be posting them in the docs with transparency soon enough.

Read and write through cache already exists today, which would work in favour of both cost, latency, and consumer reads fanout.

I like the HN Mirror over a Discord-like app for simplicity. No doubt that's where my weekend is going!