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.

Sign up for GitHub

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

Jump to bottom

feat: abstract internal database access #3856

Open

ymarcon opened this issue Jun 12, 2024 · 1 comment

Assignees

Labels

Milestone

Member

ymarcon commented Jun 12, 2024

Currently the internal database consists of a an embedded orientdb instance. The benefit of defining an abstraction layer would be:

externalize the orientdb service so that it is not affected by opal's memory usage (vertical scalability) and it can be shared by several opal instances (horizontal scalability)
use a different document-oriented database (like mongodb)
make config flexible using a plugin discovered at runtime

ymarcon added the improvement label

ymarcon self-assigned this

ymarcon added this to the opal-5.0 milestone

Member Author

ymarcon commented Jun 12, 2024 •

edited

Loading

Migrate to ArcadeDB
https://blog.arcadedb.com/welcome-to-arcadedb
https://github.com/ArcadeData/arcadedb
https://docs.arcadedb.com/#OrientDB

ymarcon modified the milestones: opal-5.0-M1, opal-5.0-M2

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment