Lightweight relational databases at the edge | RethinkConn '22

Although NATS streams solves the globally replicated and ordering problem, a sequence of messages isn't exactly queryable. What might it look like to derive a relational database from one or more streams?
NATS is a connective technology powering modern distributed systems, unifying Cloud, On-Premise, Edge, and IoT.
Join the NATS Community on Slack: slack.nats.io
Learn More about NATS at docs.nats.io/

[@billyogat]

Did this PoC ever land as a feature? I’m not seeing anything regarding this in the documentation.

[@enochabassey2786]

waaaaw. This will change the game

[@SynadiaCommunications]

We think it’s pretty neat

[@peterlarsson4875]

maybe i missed something here...but in the case of an update, how do you handle out of order events?

[@SynadiaCommunications]

There are ways to configure a stream so that you can guarantee ordering of messages being consumed

[@NaveenSiddareddy]

this is really cool. duckdb would change the analytics world

[@holgerwinkelmann6219]

Is there any activity for NATS + DuckDB in a similar setting?

[@holgerwinkelmann6219]

HI quite cool, Can we also CREATE and UPDATE from SQL ?

[@SynadiaCommunications]

Thanks! This setup materializes tables from streams, but does not support taking a new insert/update and writing it back to the stream.

[@trejohnson7677]

average gnome jedi.

[@zh4ngx]

Can't wait to try this out. Move aside ksqldb!