4 ms·
Well you can't bone a chicken drumstick very easily with a bread knife, so why would one try to use CouchDB as a relational database. I really fail to see the p
by bitdiddle 18y ago
Well you can't bone a chicken drumstick very easily with a bread knife, so why would one try to use CouchDB as a relational database. I really fail to see the point of this article, particularly given the title
- wmf 18y agoUnfortunately, I think too many people are using Fad-Driven Development where you use the newest and coolest tools even if they're totally inappropriate. The parade of articles about how Relational Databases Are Dead (even if your data is relational?) doesn't help, so I see this post as a nice counterpoint. The title is indeed trollicious.
- trezor 18y agoYour point is valid, and I wish I could give you an extra vote for coining(?) the word "Fad-driven development".
- bitdiddle 18y agoFad-Driven Development, I love it :) Sounds like a new O'Reilly book in progress. Well certainly the changing landscape of the Web has caused many to revisit the use of relational databases. There's considerable overlap with what app servers do, schemas are static beasts in general and often create application lock-in, bla, bla.. There is a fundamental tension in O-R mapping that I've concluded is best solved by dropping the R and using alternative persistence models. That said, relational databases are phenomenal and aren't going away anytime soon. I think CouchDB hits a sweet spot in a number of areas and is worth a very close look. It's still early and needs a lot of work but I think it's a keeper, especially given it's use of Erlang/OTP. Erlang is very mature and though it wasn't built with multi-cores in mind it's concurrency model is one of the few games around.