Garry Hill

Electric needs two db connections: 1. for the replication consumer, and 2. for the snapshot and schema queries When running in "embedded" mode, that is as a dependency of some...

Elixir implementation of the typescript client function. Should be droppable into a supervision tree, something like: `{Electric.Client.Materialise, client: client, shape: shape, target: target} Should be able to `reduce` the sync...

Elixir version of the (Java|Type)Script function

feat(sync-service): Remove Shapes.Monitor

1

Shapes.Monitor existed in order to be able to shutdown shape processes without returning errors to clients actively reading that shape's data. However both the registration of reader processes and the...

See #3419 Our use of mocking leaves us open to bugs in production that aren't apparent in tests. The shape recovery process is not included in the e2e tests

Inactive consumers should be put offline

1

Hibernated consumers should be put offline after some timeout, so replacing the process hibernation with process shutdown (without shape removal). This will reduce memory usage to some subset of the...

In order to prevent errors from reads to a shapes files we have a process that waits until all api read requests for a shape have terminated before terminating the...

We should only need a `stack_start_link` call to setup the storage for any given stack. `start_link` isn't needed by any impl except in-memory and this can easily be re-written to...

Now that we don't automatically start a consumer for a shape, if we receive a relation change affecting a lot of shapes we will suddenly have to start potentially a...