Timeline for How to design a database that stores large json objects
Current License: CC BY-SA 3.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Nov 15, 2017 at 17:05 | answer | added | Doc Brown | timeline score: 0 | |
| Nov 15, 2017 at 6:06 | comment | added | Esben Skov Pedersen | Just store the entire object. These crosswords seem entirely independant of each other so the things you gain from splitting them up like constraints and indeces does does not apply here. | |
| Nov 14, 2017 at 23:20 | answer | added | Archimedes Trajano | timeline score: 1 | |
| Nov 14, 2017 at 22:30 | comment | added | Austin_Anderson |
mongodb or couchdb work with documents that are json objects, but storing it this way may not be the best option, and you certainly don't have to go nosql. Consider breaking the problem up and storing pieces.
|
|
| Nov 14, 2017 at 18:51 | comment | added | Jay Elston | Have you tried modeling your application using entities and relationships? | |
| Nov 14, 2017 at 17:27 | comment | added | Doc Brown | You are probably overthinking this. In your question, there is nothing which deserves IMHO the attribute "large" (or at least, nothing large enough to make the decision between those db types important). Pick the solution you know best / which lets you implement things in the most simple way. | |
| Nov 14, 2017 at 17:15 | review | First posts | |||
| Nov 14, 2017 at 18:51 | |||||
| Nov 14, 2017 at 17:12 | history | asked | RobotEyes | CC BY-SA 3.0 |