Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Connector: Surrealdb [Source/Destination] #1594

Open
nickchomey opened this issue May 15, 2024 · 1 comment
Open

Connector: Surrealdb [Source/Destination] #1594

nickchomey opened this issue May 15, 2024 · 1 comment
Labels
connector:destination Request for a destination connector connector:source Request for a source connector

Comments

@nickchomey
Copy link

nickchomey commented May 15, 2024

Resource name

Surrealdb

Resource link

https://surrealdb.com/

Connector type

Source/Destination

Expected connector behavior

Surrealdb is a new and very promising "multi-model" database that covers relational, nosql, graph, vector, full text search, and more. This allows for consolidating many databases/stores into one, as well as affords new functionality.

One of the main obstacles to its adoption, however, is actually importing the data from numerous sources. They have an existing discussion for adding cdc to surreal, where theyve been discussing rolling their own - which makes no sense at all when Conduit exists and supports all the major databases, data stores etc...

https://github.com/orgs/surrealdb/discussions/3

Surreal also has various mechanisms for receiving live updates from the database, so it could very well be a Conduit Source as well - to feed an event driven architecture or whatever.

@nickchomey nickchomey added the triage Needs to be triaged label May 15, 2024
@hariso
Copy link
Contributor

hariso commented May 16, 2024

@nickchomey Thanks for opening this issue! SurrealDB looks like an interesting project.:) The team will definitely consider this connector. When it comes to the connectors that we implement ourselves, we prioritize based on interest shown by the dev community and based on our company's needs. However, if anybody else wants to start implementing the connector sooner than that, our team will be happy to assist with guidelines and advice.

@lovromazgon lovromazgon added connector:destination Request for a destination connector connector:source Request for a source connector labels May 17, 2024
@lovromazgon lovromazgon removed the triage Needs to be triaged label May 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
connector:destination Request for a destination connector connector:source Request for a source connector
Projects
Status: No status
Development

No branches or pull requests

3 participants