Work in progress: 181,232 of 181,233 sites checked so far, more every week · updated 2 Nov 2026Missing a blog? Tell us

Top all-time · #5767

E

Epsio

Company blog · epsio.io/blogprogrammingdata

Epsio is the company blog at epsio.io, writing about programming and data. Since 2023, 14 different Hacker News readers have linked it 40 times, most often “How To Build a Streaming Engine”. No feed was found, so read it on the site itself.

No feed foundVisit the blog
40mentions?
14HN people?
2023–2025first – last linked?
Links on Hacker News per year · peak 16 in 2023

Too few sampled comments (2) to say how often HN recommends it.?

Why HN links it

HN readers link Epsio's product pages on incremental views for existing databases, a streaming transformation tool. Comments discuss incremental view maintenance and Epsio's dataflow engine.

Summarised by Claude from a sample of 2 HN comments that link here. Each comment is marked recommending, critical or neutral (citing without judging); how this works.

Deliver instant and always up-to-date results for complex queries with Epsio’s streaming SQL engine.

Most-linked posts?

  1. How To Build a Streaming Engine
    5 people · 5 mentions · first linked 2023-09-28
  2. Epsio Outperforms Apache Flink by Up to 21x on TPC-DS Dataset
    3 people · 3 mentions · first linked 2025-01-29
  3. Epsio's Diff in the Streaming Landscape
    2 people · 4 mentions · first linked 2023-11-14
  4. Thoughts on the Future of Stream Processing
    2 people · 3 mentions · first linked 2025-06-17
  5. Memory Management in a Streaming SQL Engine
    2 people · 2 mentions · first linked 2024-01-09
  6. Why is stream processing hard?
    2 people · 2 mentions · first linked 2025-06-18
  7. Out of Memory Shenanigans
    2 people · 2 mentions · first linked 2024-01-05
  8. Optimizing Streaming JOINs: Leveraging Asymmetry for Better Performance
    2 people · 2 mentions · first linked 2025-02-10

What Hacker News says?

  1. This looks extremely cool. This is basically incremental view maintenance in databases, a problem that almost everybody (I think) has when using SQL databases and wanting to do some derived views for more performant access patterns. Importantly, they seem to support a wide breath of SQL operators, support spilling computation state to disk, and it's open-source! Interestingly, it compiles queries to Rust, so an appr…

    Comment linking /

    on “Feldera Incremental Compute Engine”
  2. Submitted Out of Memory Shenanigans as a story · 32 points

    HN discussion
  3. Hi! - 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 sa…

    Comment linking /blog/epsios-diff-in-the-streaming-landscape

    on “Show HN: Epsio – Incremental views for your existing database”
  4. Submitted Thoughts on the Future of Stream Processing as a story · 7 points

    HN discussion
  5. Submitted Optimizing Streaming JOINs: Leveraging Asymmetry for Better Performance as a story · 7 points

    HN discussion
  6. Submitted Why is stream processing hard? as a story · 6 points

    HN discussion
  7. Submitted Epsio Outperforms Apache Flink by Up to 21x on TPC-DS Dataset as a story · 4 points

    HN discussion
  8. Submitted Epsio Outperforms Apache Flink by Up to 21x on TPC-DS Dataset as a story · 4 points

    HN discussion
  9. Submitted Scaling PostgreSQL for Complex Queries as a story · 4 points

    HN discussion
  10. Submitted Out of Memory Shenanigans as a story · 4 points

    HN discussion
  11. Submitted Why We Built a Streaming SQL Engine as a story · 4 points

    HN discussion
  12. Submitted Is It Time to Rethink Stream Processing? as a story · 3 points

    HN discussion
  13. Submitted A 7x faster Flink alternative as a story · 3 points

    HN discussion
  14. Submitted MySQL Slow Query Log as a story · 3 points

    HN discussion
  15. Submitted Memory Management in a Streaming SQL Engine as a story · 3 points

    HN discussion
  16. Submitted The gap between the data we store and the data we need as a story · 3 points

    HN discussion
  17. Submitted How To Build a Streaming Engine as a story · 3 points

    HN discussion
  18. Submitted Epsio – streaming transformations made easy as a story · 2 points

    HN discussion
  19. Submitted Stream processors and ease of use as a story · 2 points

    HN discussion
  20. Submitted The Future of Data Streaming as a story · 2 points

    HN discussion
  21. Submitted A 7x faster Flink alternative as a story · 2 points

    HN discussion
  22. Submitted Why Streaming SQL? as a story · 2 points

    HN discussion
  23. Submitted Building a Streaming SQL Engine as a story · 2 points

    HN discussion
  24. Submitted How We Built a Streaming SQL Engine as a story · 2 points

    HN discussion
  25. Submitted How We Built a Streaming SQL Engine as a story · 1 points

    HN discussion
  26. Submitted The Future of Stream Processing as a story · 1 points

    HN discussion
  27. Submitted Making streaming joins 50% faster as a story · 1 points

    HN discussion
  28. Submitted Floating Points in Streaming Systems as a story · 1 points

    HN discussion
  29. Submitted Streaming SQL Arithmetic: The Horror as a story · 1 points

    HN discussion
  30. Submitted Memory management in a streaming engine as a story · 1 points

    HN discussion

Search all of HN for epsio.io