---
title: "Gilad Kleinman (@giladkl) | Hashnode"
description: "Gilad Kleinman (@giladkl) writes on Hashnode. Read their latest articles and follow their work."
url: "https://hashnode.com/@giladkl"
---

@giladkl

# Gilad Kleinman

@giladkl · Joined January 2025

### [Why is stream processing hard?](https://blog.epsiolabs.com/why-is-stream-processing-hard?utm_source=hashnode&utm_medium=feed)

Before starting Epsio a couple of years ago, I used to spend countless hours learning about creative and innovative ways companies were making data access and querying faster and more efficient. Looking at rising products in that space — whether it’s...

10 min read · [blog.epsiolabs.com](https://blog.epsiolabs.com/why-is-stream-processing-hard?utm_source=hashnode&utm_medium=feed)

[Aug 10, 2025](https://hashnode.com/posts/why-is-stream-processing-hard/6898bc4e85afd18ab297eb68)

### [The Bidirectional Stream Processor: Why Pull Beats Push for Crash Recovery](https://blog.epsiolabs.com/building-a-recovery-mechanism?utm_source=hashnode&utm_medium=feed)

At Epsio — we’re building a streaming SQL engine, focusing our engineering effort towards ease of use / removing the middleware usually associated with stream processing. As part of that effort — we need to ensure that if and when our stream processo...

7 min read · [blog.epsiolabs.com](https://blog.epsiolabs.com/building-a-recovery-mechanism?utm_source=hashnode&utm_medium=feed)

[Aug 5, 2025](https://hashnode.com/posts/building-a-recovery-mechanism/6891ee53be2b6a9cda94016b)

### [Why We Built a Streaming SQL Engine](https://blog.epsiolabs.com/why-we-built-a-streaming-sql-engine?utm_source=hashnode&utm_medium=feed)

Following our previous blog post “How we built a Streaming SQL Engine,” we are delighted to share some of the reasoning and thoughts that led us to build Epsio (as we always say — start with how, only later ask why). Why we built Epsio For most of ou...

8 min read · [blog.epsiolabs.com](https://blog.epsiolabs.com/why-we-built-a-streaming-sql-engine?utm_source=hashnode&utm_medium=feed)

[Aug 21, 2024](https://hashnode.com/posts/why-we-built-a-streaming-sql-engine/687fb2fc516e3a695c757d6d)

### [Out Of Memory Shenanigans](https://blog.epsiolabs.com/out-of-memory-shenanigans?utm_source=hashnode&utm_medium=feed)

At Epsio Labs, we develop an incremental SQL engine — in brief, an SQL engine that operates on changes instead of reprocessing the whole dataset each time a query runs. I’ll leave explaining why that’s useful to another blog post of ours — Why We Bui...

17 min read · [blog.epsiolabs.com](https://blog.epsiolabs.com/out-of-memory-shenanigans?utm_source=hashnode&utm_medium=feed)

[Aug 6, 2024](https://hashnode.com/posts/out-of-memory-shenanigans/687fb030a5343886b5e2a1dc)
