Thanks! Yes, avoiding glue code was a key goal, as I wanted to see what was possible with pure configuration. I'm curious about your WebSocket challenges - did something like Benthos help, or did you end up rolling your own from scratch?
On latency: I didn't do a head-to-head with RisingWave, so I can't really comment. There's definitely a latency cost for strong consistency, but for this use case, it seemed a good trade off — you never see incorrect intermediate values, and views are composable since they're all aligned to the same point in time. But if you're optimizing for end-to-end latency, and want to stay in SQL-land, RisingWave might be the better fit.
Thanks! Yes, avoiding glue code was a key goal, as I wanted to see what was possible with pure configuration. I'm curious about your WebSocket challenges - did something like Benthos help, or did you end up rolling your own from scratch?
On latency: I didn't do a head-to-head with RisingWave, so I can't really comment. There's definitely a latency cost for strong consistency, but for this use case, it seemed a good trade off — you never see incorrect intermediate values, and views are composable since they're all aligned to the same point in time. But if you're optimizing for end-to-end latency, and want to stay in SQL-land, RisingWave might be the better fit.
P.s. Part 2 is out: https://tycoworks.substack.com/p/can-a-streaming-database-power-a-f49