141–150 of 173 posts
Earlier quoted context omitted.
It is in Firefox. The SQLite team has been working on making WASM support first class, so should work anywhere WASM does.
Ok, so are you saying that currently Electric SQL only works with Firefox, but NOT with Google Chrome?
We assessed nearly every new data solution available and ultimately chose Electric. We recognized that the combination of SQLite's convenience on the client-side and PostgreSQL's flexibility on the server-side is a potent foundation for our work.
I've spent years grappling with the challenges of the local-first (lo-fi) approach, particularly when using the PouchDB CouchDB combination to support vital offline features in our Point of Sale tools. While not every feature aligns with the lo-fi concept (even though real-time synchronization status on the client can significantly reduce the need for numerous API end points), having PostgreSQL on the backend grants us access to a wealth of existing tools and support built around PostgreSQL. This assurance provides us with peace of mind, knowing that we won't encounter insurmountable obstacles, and any challenges we face will be no more daunting than those encountered in traditional server-based API programming paradigms.
I sincerely hope that ElectricSQL achieves the recognition it deserves and can implement many of the ideas outlined in their roadmap documentation. These ideas have the potential to overcome the initial hurdles that have hindered the widespread adoption of the lo-fi approach.
In the meantime, we're having a great time developing an opinionated, React-based low-code tool (internally, we refer to it as "Visual Basic using React"). We're looking forward to leveraging some of the outstanding work done by James' team thus far!
Or is there a better tool for that?
[1]: https://electric-sql.com/docs/usage/data-access/shapes#data-loadingProduct looks excellent, and your website is gorgeous. Kudos! It looks like the "Switch from X" buttons don't go anywhere.
Earlier quoted context omitted.
I don’t disagree with your technical assessment per se but I would would not label any of this “pretty simple”, except for special purpose apps with technically competent users. Academically it’s in a decent state, but tech- and UX wise I’d say it’s immature. It virtually penetrates all layers of a normal stack (including layer 8). For apps it’s at least possible but the web is very tricky as a platform for anything…
I do agree that the UX of a lot of E2EE software is pretty bad, and if you wanted to make e.g. a chat application, then yeah, it's not necessarily "simple". In practice it can become quite a mess. And honestly, I think a lot of apps have just done a poorer job than what would've been possible without much hassle because it's relatively new territory for a lot of developers. On the other hand though, we're talking in…
I'm interested in your calculation for compute cost savings. You have savings of 40k$ for 2k queries per second. I'm currently using GCP CloudSQL (Postgres) and have > 2k requests per second (for tables with billions of rows) for 200$/month. Is there a scenario that I'm overlooking?
Edit: Saw the explanation on your website. Apparently you're comparing it to AWS Aurora which charges for the amount of queries.
Congrats to the team. Very nice project. I'm interested in your calculation for compute cost savings. You have savings of 40k$ for 2k queries per second. I'm currently using GCP CloudSQL (Postgres) and have > 2k requests per second (for tables with billions of rows) for 200$/month. Is there a scenario that I'm overlooking? Edit: Saw the explanation on your website. Apparently you're comparing it to AWS Aurora which c…
edit: we based some of the calculator variables on https://fauna.com/blog/compare-aws-aurora-serverless-v2-arch...
Congrats. How does this deal with schema changes? We have a solution where old clients can store objects that have new fields unknown to the client. Then when the clients updates the data is visible. Do you have client libraries for mobile? Swift & Kotlin? Does it support partial sync and fetch when you need an “archived” item? In my experience you only want the “working set” of data on the client. Not everything. Co…
You can learn more about our support for migrations here: https://electric-sql.com/docs/usage/data-modelling/migration...
Native clients will be coming a bit later.
You can use the shapes to control what data syncs to the device: https://electric-sql.com/docs/usage/data-access/shapes