Timeline for Why use a database instead of just saving your data to disk?
Current License: CC BY-SA 3.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 12, 2017 at 7:31 | history | edited | CommunityBot |
replaced http://programmers.stackexchange.com/ with https://softwareengineering.stackexchange.com/
|
|
| S Feb 23, 2014 at 19:06 | history | suggested | Peter Mortensen | CC BY-SA 3.0 |
Copy edited (but more work is needed near "until you SQL"). Expansion. Added some context.
|
| Feb 23, 2014 at 18:52 | review | Suggested edits | |||
| S Feb 23, 2014 at 19:06 | |||||
| May 19, 2013 at 12:58 | comment | added | gbjbaanb | @Dokkat so you don;t use MySql or any other full-featured "server" style DB. You use Sqlite (or similar) and it will persist to disk every time, whilst giving you a DB embedded in your app (so no need for a separate install) and still giving you sql access, transactional integrity and disk persistence. | |
| May 18, 2013 at 22:45 | comment | added | mikerobi | @Dokkat, I hope that nobody kicks the power cord in between depositing funds in your bank account and "periodically" writing the account balance to disk. You've described a guaranteed data loss architecture. That is fine for some applications, but most database applications give users the power to choose. You can run a single database node with backups and risk some data loss or use replication to eliminate data loss if a single node fails. | |
| Mar 15, 2013 at 15:37 | comment | added | alroc | Don't judge RDBMSs by what happened with a single application that was probably coded poorly. Especially when the modifications to support a database were made by someone with no database experience. | |
| Mar 15, 2013 at 1:20 | comment | added | MaiaVictor | Mysql simply couldn't handle fully saving state each 2 minutes or so. It was pretty clear when the saving happened - the whole server "lagged" for a second. Now I'd really appreciate if people posting here had an answer for that one! | |
| Mar 15, 2013 at 1:18 | comment | added | MaiaVictor | Just to note, I've actually used mysql for years when I hosted an "otserv". Guess what? All it brought was problems. People could "clone" items using a dirty trick after they realized their characters was saved when they logged out but not when the server crashed. This is a serious problem for otservs. And the otserv community is HUGE. That wouldn't happen if they just stored data on memory and serialized it periodically. So I modified the source by myself, those long C++ files and started saving to mysql periodically, instead of when characters logged out. Guess what? It was SLOW! | |
| Mar 14, 2013 at 16:56 | history | answered | JeffO | CC BY-SA 3.0 |