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

Substitution of PhyloDB for a custom SQL database #19

Open
andre-j3sus opened this issue Jan 30, 2024 · 0 comments
Open

Substitution of PhyloDB for a custom SQL database #19

andre-j3sus opened this issue Jan 30, 2024 · 0 comments
Assignees

Comments

@andre-j3sus
Copy link
Member

This change involves discarding the PhyloDB database, which uses the graph-based database Neo4j, and opting for a new database server implementation utilizing a different approach for data storage, like SQL.

Weaknesses of using PhyloDB include:

  • performance and latency issues related to the communication with Neo4j for the storage of data;
  • it being an incomplete prototype that isn't ready to be used consistently, needing adjustments, fixes and implementations of features required of our platform;
  • a SQL database might be more easy to debug and maintain and the use of a graph-based database might not be justifiable for the scope of this project and the data at hand.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants