There are a few issues, but the most frustrating one is the inability to reload the page or close the tab. If you accidentally do either of these, any changes made since the last version was saved on the cloud while you were online will be lost. Sometimes, if you switch online and you are writing, you could lose everything.
You're right. It's a closed Beta at this point, so feel free to drop your email, and we'll open a user for you. Soon we'll release an open beta where everyone can sign up and start using.
Reg the demo, there might be a chance that in the demo, you got the response from a location that is close to you but not the closest. The product version is well-optimized. I hope it helps.
Generally speaking, Edginary pulls data from various sources like databases, data lakes, and data warehouses using Change Data Capture (CDC) or periodic polling mechanisms. This ensures up-to-date data ingestion in real-time or near-real-time.
Once the data is captured, Edginary enables users to combine, transform, and aggregate it using its own internal real-time transformation engine. It supports Streaming SQL, with future plans to incorporate WebAssembly and TypeScript.
After processing, the processed data is replicated to hundreds of nodes worldwide, stored, and indexed in a low-latency datastore, queryable using REST API with millisecond response time globally.
We're currently supporting Postgres & MySql and will support more. You can register for our Beta and try it yourself at https://www.edginary.io/beta
Thanks Joe. Per your questions - 1) You should get an official invite on April 1st, this is when we open our closed beta. 2) Integrating with Kafka and writing code will be part of our next version. 3) There are a few major changes, but I'll just say that we aim to provide an end-to-end solution that not only improves your DB performance but also brings the data closer to your users to avoid network latency while keeping your data always up to date.
