3 ms·
If you have a graph, then a graph database How does one know if it's time to migrate to a graph database? Right now I have a large (6.5GB) database that I hav
by reaperducer 8y ago
If you have a graph, then a graph database
How does one know if it's time to migrate to a graph database?
Right now I have a large (6.5GB) database that I have to sometimes work with, and the queries are getting more complex as more features are added to the project.
Right now the data is stored in MySQL, but to get anything interesting out of it requires multiple queries and then sifting through the data later. It all seems cumbersome.
- deleted 8y ago[deleted]
- unixhero 8y agoBetter port that sucker to Postgres sooner rather than later. You know, for future proofing.
- chadcmulligan 8y agoIt depends on the structure of the DB - 6.5GB is large if its attributes, if its documents then not so much. If its an index of documents then a different problem. Access patterns matter to. Like if its a 6.5 GB database that stores OLTP data, then yes thats large. If its a history of document modifications then probably small. If its historical data for a data cube sort of app, then its pretty small, I'd say tiny - I've worked on ones that get into the TB's.
- reaperducer 8y agoIt's all attributes; no documents being stored. About 2m records.
- chadcmulligan 8y agoSo thats a bit over 3k per record. Forgive my curiosity but whats the application domain? Thats a lot of info per record.