41–50 of 76 posts
Well done guys. But don't forget to credit Bryant Cutler ( http://bryantcutler.com/ ) for the awesome logo. update: downvoted? why? I really think the guy should be credited. He did a fricking awesome job which CouchDB has based its whole image on. The faux movie poster linked at the top of this story has a giant size version of his logo as the very backdrop. This shit is important. Credit him, says I!
Congrats, guys! I have to say, though, while you were busy inching towards 1.0 I've fallen in love with other production-ready NoSQL db's (namely Mongo and Cassandra). I'm excited to play with Couch, just to play with it, but as someone who is already very satisfied with other NoSQL technologies (when I need them), what would be your pitch for why I should give Couch a serious look?
I think we have different definitions of "production-ready." I find Cassandra to considerably immature having weird bugs that cause it to outright crash and both Cassandra and Mongo have seen issues from many people with data loss. Yes, people are using these systems in production but they're both still young and immature and it is in everyone's best interest to continue to evaluate possible solutions that are coming…
Can someone give me a quick synopsis of what I would use this for? Is this only for Facebook size scaling or is it of use for those of us just starting out?
I'm not a CouchDB pro by any means but I've been following it from a distance for some time. The main feature of CouchDB is that it's a fast, scalable database that also allows you to host your apps inside of it, with each "view" being stored in the database itself. I believe some people use it for large installations but as far as I know that is not the primary focus.
While I haven't used couchdb much personally, its most significant characteristics seem to be that it's a document-oriented database (each record can have its own structure) and that it inherits all of Erlang's infrastructure for fault-tolerance.
Well done guys. But don't forget to credit Bryant Cutler ( http://bryantcutler.com/ ) for the awesome logo. update: downvoted? why? I really think the guy should be credited. He did a fricking awesome job which CouchDB has based its whole image on. The faux movie poster linked at the top of this story has a giant size version of his logo as the very backdrop. This shit is important. Credit him, says I!
I down-voted you just now because you complained about being down-voted, which isn't good etiquette.
Earlier quoted context omitted.
I'm not a CouchDB pro by any means but I've been following it from a distance for some time. The main feature of CouchDB is that it's a fast, scalable database that also allows you to host your apps inside of it, with each "view" being stored in the database itself. I believe some people use it for large installations but as far as I know that is not the primary focus.
It's a "fast, scalable database" that isn't focused on large installations? What? While I haven't used couchdb much personally, its most significant characteristics seem to be that it's a document-oriented database (each record can have its own structure) and that it inherits all of Erlang's infrastructure for fault-tolerance.
Earlier quoted context omitted.
I think we have different definitions of "production-ready." I find Cassandra to considerably immature having weird bugs that cause it to outright crash and both Cassandra and Mongo have seen issues from many people with data loss. Yes, people are using these systems in production but they're both still young and immature and it is in everyone's best interest to continue to evaluate possible solutions that are coming…
I've been in production without issue for years in some installations. I probably could have raised the "production-ready" flag in 2008/2009 if I held myself to the same standards as a lot of projects.
After looking into Erlang for a while now (still in chapter 3 of ERLANG Programming by Francesco Cesarini) I have to state that writing something this big in Erlang was bold, really, really bold. Erlang is not really that fun or exciting to use
It depends what you use it for. Its brilliant for infrastructure - software that has to live forever and survive no matter what gets thrown at it. It makes a lot of the hard problems go away so you can focus on the fun and exciting stuff.
I think it is pretty cool that http://couch.io/ is a website served directly by CouchDB. Server: CouchDB/0.12.0ab71f475-git (Erlang OTP/R13B)
HTTP/1.1 200 OK Date: Wed, 14 Jul 2010 19:28:23 GMT Server: Apache X-Powered-By: PHP/5.2.6-1+lenny8 Vary: Accept-Encoding Connection: close Content-Type: text/html
Unknown Domain