aspen

ow my lungs ow oof ouch

love to hear it!!

hopefully will set aside time to blog about some of that testing soonish ;)

The situation is somewhere in between those two - there are definitely some issues that I know about that would give me hesitation recommending depending on RS for production traffic atm for some workloads - but we also do quite a bit of generative + chaos testing which gives me more confidence.

we don't currently have an exhaustive list publically documented, but we're currently working on an internal version of something like that list - I'll float publishing something like that.

lmk if I can help at all!

https://docs.readyset.io/guides/intro/quickstart/#step-1-start-readyset very easy (we hope at least)

with `--standalone` or `STANDALONE=yes` you can just run the whole thing as a single binary

also if you wanna run on a single node (eg, don't need scalability past 1M QPS or HA) you don't need a CP meta-store at all

hi i made a realname account idk how much I'll use it but it's good to be able to talk about work here it seems

there's sharp edges for sure but we're actively working on fixing them

eep

ReadySet has switched over our CP metadata backend to Consul.

hi! made a (work-facing??) bsky account to reply to this but I'm employee #2 at ReadySet. It's not fully production ready yet but we're actively working on making that happen, and in the meantime we really love people trying things out (it's ~open source!). Happy to answer any questions.

hi its me