Date: Tue, 02 Jul 2013 06:55:39 -0500 From: "Mark Felder" <feld@feld.me> To: freebsd-questions@freebsd.org, "Ivan Voras" <ivoras@freebsd.org> Subject: Re: sleepycat db VS MySQL or postgres Message-ID: <op.wzlfe12e34t2sn@tech304.office.supranet.net> In-Reply-To: <kqub0l$8pk$1@ger.gmane.org> References: <51D1E68B.5050508@paz.bz> <kqub0l$8pk$1@ger.gmane.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 02 Jul 2013 05:45:47 -0500, Ivan Voras <ivoras@freebsd.org> wrote: > Well, this is essentially a bikeshed thread... so why not chip in I disagree; all of these databases have distinctly different uses. MySQL/PostgreSQL: pick your poison. Relational databases. Will you have multiple users connecting to the database? Will there be lots of updates to the data? These are what you want. If you care about data integrity, I'd choose Postgres. SQLite: Do you want a relational database without needing a daemon to be running and will only have a single user/process accessing the database at one time? This is what you want. NoSQL: Do you want to dabble with the mess that is NoSQL so you can build your "cloud"? Don't care if other nodes aren't guaranteed to get the latest copy of the data? This is what you want. SleepyCat/BerkleyDB: Is your data WORM? (Write Once Read Many) If so, this is *ABSOLUTELY* what you want. If twitter was built upon a WORM database instead of MySQL they could host the entirety of twitter on a handful of servers instead of the gross MySQL+Cassandra mess they're fighting with today.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?op.wzlfe12e34t2sn>