_ben_

10 ms·

1.
by _ben_ 5mo ago
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: Mermaid/SVG/PNG gets emitted, but there’s no dur
2.
Zindex – Diagram Infrastructure for Agents(zindex.ai)
58 points by _ben_ 5mo ago|16 comments
3.
by _ben_ 5mo ago
Zindex is a stateful diagram runtime for agents. Agents create diagrams by sending structured operations through the Diagram Scene Protocol (DSP) - the platform validates, normalizes, and renders durable scene state rather than one-shot out
4.
Show HN: Edge HTTP to S3, now with schema-aware Parquet(edge.mq)
1 points by _ben_ 8mo ago|0 comments
5.
by _ben_ 9mo ago
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 S3’s API, it’s what you need around S3 when you have lots of
6.
Show HN: Edge HTTP to S3(edge.mq)
2 points by _ben_ 9mo ago|2 comments
7.
by _ben_ 3y ago
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 get set accordingly and are set per SQL query. The model
8.
by _ben_ 3y ago
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 use caching to store data and run SQL compute at the edge.
9.
by _ben_ 3y ago
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 the app tier. The Smart Invalidation feature inspects updates&
10.
by _ben_ 4y ago
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 data from the cache, globally. You can read more here: http
11.
by _ben_ 4y ago
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 zero configuration or sizing etc. 1. https://www.
12.
Regional execution for ultra-low latency rendering at the edge(vercel.com)
3 points by _ben_ 4y ago|0 comments
13.
Debezium Server with PostgreSQL and Redis Stream(egkatzioura.com)
3 points by _ben_ 4y ago|0 comments
14.
Deterministic Databases and the Future of Data Sharing(thenewstack.io)
2 points by _ben_ 4y ago|0 comments
15.
Deploying a Node app and Postgres database to Fly.io(simonplend.com)
5 points by _ben_ 4y ago|0 comments
16.
by _ben_ 4y ago
Does CF workers support TCP yet?
17.
by _ben_ 4y ago
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 connect your database and then have global low-latency read
18.
by _ben_ 4y ago
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 simplicity, until access patterns change. We focus on distribut
19.
Database Read Replicas vs. Database Edge Caching(polyscale.ai)
1 points by _ben_ 4y ago|0 comments
20.
Distributed Caching on Cloud(thenewstack.io)
2 points by _ben_ 4y ago|0 comments
21.
Scaling GraphQL with Redis Consumer Groups(parabol.co)
2 points by _ben_ 4y ago|0 comments
22.
by _ben_ 4y ago
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, MS SQL Server (more coming including no-sql). It has a glo
23.
Welcome to the New Database Era(ethanjb.medium.com)
3 points by _ben_ 4y ago|0 comments
24.
Handling Data at the Edge with Cloudflare Workers(launchdarkly.com)
11 points by _ben_ 4y ago|0 comments
25.
The beginning of the unbundled database era(techcrunch.com)
1 points by _ben_ 4y ago|0 comments
26.
by _ben_ 4y ago
PolyScale | Remote (GMT -8 to GMT +3) | Full-time | https://www.polyscale.ai/ Founding team hires. PolyScale is changing how databases are distributed and scaled. Our mission is to enable edge-first data by simplifying glob
27.
by _ben_ 4y ago
PolyScale | Remote (GMT -8 to GMT +3) | Full-time | https://www.polyscale.ai/ Founding team hires. PolyScale is changing how databases are distributed and scaled. Our mission is to enable edge-first data by simplifying glob
28.
by _ben_ 4y ago
That’s right. Currently the auto invalidation is somewhat of a blunt instrument in that it will blow away all cache data related to the table(s) as default. That approach favors consistency over performance, but is also a natural fit to som
29.
by _ben_ 4y ago
We're building PolyScale[1] to address this problem. PolyScale is a serverless edge cache for databases so you can easily distribute your reads. We are opening up early access to our connection pooling features in the next couple of we
30.
Cache Is the Root of All Evil (2020)(medium.com)
1 points by _ben_ 4y ago|0 comments

More ›