Flutterby™! : Goodbye CouchDB

Next unread comment / Catchup all unread comments User Account Info | Logout | XML/Pilot/etc versions | Long version (with comments) | Weblog archives | Site Map | | Browse Topics

Goodbye CouchDB

2012-09-23 15:00:03.023116+00 by Dan Lyke 3 comments

Sauce Labs: Goodbye CouchDB. Turns out using not-a-database for your database causes problems.

I think there's even a deeper issue here: If you think that not having a schema and structure to your data is a good idea, you probably don't really understand how to structure your data.

[ related topics: Interactive Drama Databases ]

comments in descending chronological order (reverse):

#Comment Re: made: 2012-09-25 15:01:23.051781+00 by: Dan Lyke

Yeah, arbitrary key-value pairs is a clear indication that someone doesn't really understand their data yet. There's a time and a place, but structure really can help...

#Comment Re: made: 2012-09-25 03:07:48.90235+00 by: ebradway

I've been dealing with not-a-database concepts in OpenStreetMap. Ostensibly, OSM uses PostgreSQL on the backend. But the meat of the data is tied up in arbitrary key- value pairs. The result is my code has to deal with two levels of impedance mismatch. Python does a good job of softening the blow of the set-orientation mismatch. But I'm stuck doing a lot of searching in code that I would have expressed in SQL if the key-value pairs were actual fields.

NoSQL appears to work well in environments where you want the crowd to rapidly construct data schemata. But once the schemata are firmed up, commit them to SQL! Ironically, OSM does this nightly when it exports the data to PostGIS in order to render tiles.

#Comment Re: made: 2012-09-23 23:29:09.526147+00 by: meuon

Nice article, realistic assessment/use of MySQL.