Closed whitesoup12 closed 3 months ago
Have you considered using a graph database instead? There are certain relationships between objects and with a graph DB performing the "join" at WRITE (rather than SQL doing the JOIN at READ), the database would be really fast - easily under 8ms if not as fast as 2ms. I may be biased since I work for Neo4j, and I would be happy to take a look at what you are solving for and provide advice. I have been in the database business for 30+ years and can be a sounding board.
Moving from MySql to MongoDB for several reasons:
During this transition a lot of data will be renamed to make more sense based on how it's used. Eg. Playlist is used when it's actually sequence.