[Discussion] Future of Electric after Databricks?

Open
#4,770 0 comments 7 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
20/100
Issue type
Documentation
Clarity
Needs clarification
Activity status
Active
Tech stack
postgresql

Research direction

The issue asks maintainers about Electric Sync's future, update policy, archival status, and self-hosting path after the Databricks acquisition. No file, test, implementation entry point, or acceptance criteria is identified, so there is no concrete starting point or defined done state for a contributor.

Written by the indexing model from the issue text.

Description

Hi good people!

First of all, thank you to all the contributors for building this amazing service/product.

Does anyone know what will be the future of electric sync and other products after the acquisition by Databricks?

I read the official statement saying Everything Electric has previously open sourced stays open source: Postgres Sync, PGlite, TanStack DB, Durable Streams.

but I'm still a little worried.

  • will the electric sync project keep getting updates?
  • will it not be archived/deprecated?
  • can we reliably self-host electric sync? is there a paved path?

Thanks a bunch!

Dominant language
TypeScript
Stars
10.4k
Forks
399
PR merge metrics
No merged PRs in 30d

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from electric-sql/electric

All issues in electric-sql/electric

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.