electric
electric copied to clipboard
electric-sql
Sync little subsets of your Postgres data into local apps and services.
This will make it easier for contributes to download the repo and install packages using the required package manager. Bonus points for adding an `.nvmrc` to make it easy to...
There is a large compute overhead for evaluating shape where clauses. What are the performance numbers we're looking into? The shape matching algorithm should be able to evaluate a single...
Currently, Electric stores an initial snapshot and a shape log for every shape. However, the snapshot is a sequence of inserts and thus can be stored in the shape log,...
narrative: - loads relatively fast - client-side interactivity is very fast - works offline - loads very fast with cached data/code
Idea is to start collecting data from GH so that in some time we can have loads of data we can user for some nice live analytics.
When a table is dropped from Postgres, users currently need to manually delete all shapes that are defined on that table. This is needed to avoid any problems that would...
Every insert, update, delete operation is written to the log. Eventually this means every shape log will hold a lot of redundant information e.g. 10 updates to the same row...
The password needs to be obfuscated such that when ConnectionManager crashes and its state is logged, the password is not visible in the log output.
Imagine a simple scenario where Electric is running inside a Kubernetes pod with no persistent storage. Some shapes get created, so Electric creates a publication in Postgres and starts processing...
Metadata
Owner
Metadata
Sync little subsets of your Postgres data into local apps and services.