Comments URL: https://news.ycombinator.com/item?id=50318720

Points: 208

# Comments: 65

Comments URL: https://news.ycombinator.com/item?id=50005013

Points: 3

# Comments: 1

Comments URL: https://news.ycombinator.com/item?id=44298972

Points: 1

# Comments: 0

- Actually, Epsio has its own dataflow engine. It's based on much of the same theory as these other technologies, we just found that their implementation doesn't quite fit our use case neatly.

Just as an example, Timely/Differential dataflow requires saving state in memory. While this results in extremely low latency (beneficial for its original purpose), the trade-off is the high memory footprint required to save state for complex SQL queries (JOINS, DISTINCT ON, etc.). We found this to be quite costly for the use case of replacing heavy SQL queries in PG/MySQL.

We actually recently published a blog post on how we see the streaming landscape -https://www.epsio.io/blog/epsios-diff-in-the-streaming-lands... , welcome to take a look for our full thoughts :)

- Regarding SQL support, we support today DISTINCT [ON], UNIONs, JOINs, CTEs, ORDER BYs, GROUP BYs, and some additional operators/functions (full list is in this link: https://docs.epsio.io/sql-support/queries/)

Window functions are supposed to be released soon :)

Comments URL: https://news.ycombinator.com/item?id=39089007

Points: 24

# Comments: 6

Comments URL: https://news.ycombinator.com/item?id=38928097

Points: 3

# Comments: 0

Comments URL: https://news.ycombinator.com/item?id=38925560

Points: 32

# Comments: 5