Viewing profile — _ben_

I’m building Zindex [1], which is aimed at this exact “visual representation of executable workflows” layer. What I'm solving for is AI-generated diagrams are usually one-shot: Mer…

Zindex is a stateful diagram runtime for agents. Agents create diagrams by sending structured operations through the Diagram Scene Protocol (DSP) - the platform validates, normaliz…

Hi HN, TL;DR: POST JSON to an HTTP endpoint. Get Parquet and compressed segments in your S3 bucket. No Kafka, no Kinesis, no glue code. EdgeMQ ingests newline delimited JSON from o…

Thanks for the question. You’re right that S3 itself is simple and reliable, and yes, most engineers *can* write HTTP retries and multipart uploads. EdgeMQ isn’t trying to replace …

Hi HN, Edge.mq makes it very easy to ship data from the edge to S3. EdgeMQ is a managed HTTP to S3 edge ingest layer that takes events from services, devices, and partners on the p…

Thanks for the questions. At a very high level, the AI uses statistical models that learn in real-time and estimate how frequently the data on the database is changing. The TTL's g…

At PolyScale [1] we tackle many of the same challenges. Some of this article feels a little dated to me but the data distribution, connectivity and scaling challenges are valid. We…

PolyScale [1] focuses on many of these issues. It provides a globally distributed database cache at the edge. Writes pass through to the database and reads are cached locally to th…

Yes, in the early versions of the automated invalidation, the logic cleared all cached data based on tables. That is no longer the case. The invalidations only remove the affected …

For database caching outside of PlanetScale, PolyScale.ai [1] provides a serverless database edge cache that is compatible with Postgres, MySQL, MariaDB and MS SQL Server. Requires…

Does CF workers support TCP yet?

PolyScale founder here. Assuming you are referring to PolyScale (rather than ClickHouse), the product is aimed at devs who dont want to build data distribution and caching. You can…

Disclaimer: I am the founder of PolyScale [1]. We see both use cases: single large database vs multiple small, decoupled. I agree with the sentiment that a large database offer sim…

PolyScale [1] is a serverless plug-and-play database edge cache. Our goal is for devs to be able to scale reads globally in a few minutes. It’s wire compatible with Postgres, MySQL…