Timeline for Why use a database instead of just saving your data to disk?
Current License: CC BY-SA 3.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Mar 14, 2013 at 13:42 | comment | added | MaiaVictor | which I guess I am. For example, when I transform data from "player list" to "ranking", this is nothing but a map reduce operation. When creating a game or an interactive site, pretty much everything you present is a mapReduce operation from your core data! So having that kind of optimization could be really desirable. Well, I have no idea if any of what I'm talking proceeds, but that makes sense. Learning a lot today, and I'm really liking the NoSQL concepts. Thanks for the answer (: | |
| Mar 14, 2013 at 13:37 | comment | added | MaiaVictor | To be honest I love this answer and would like that to be true, but I'm not sure that's the case. For example, some users (and you) raised a concern about memory. Of course, if I'm storing GBs worth of data I can't keep it all on memory. But what if I'm certain the data would never be that large, should I just use memory? Well, there are other things too. For example, I've learned about CouchDB's incremental views. That is certainly something that, differently from indexing, would NOT be trivial to implement yourself, and is certainly a huge speedup when you are using a view model, | |
| Mar 14, 2013 at 12:44 | review | First posts | |||
| Mar 14, 2013 at 12:46 | |||||
| Mar 14, 2013 at 12:26 | history | answered | funql.org | CC BY-SA 3.0 |