bigcouch

Cloud, everybody wants it, some actually use it. So what’s my take away from AWS’ recent outtage? Background So first off, we had two pieces of our infrastructure failing (three if we include our Multi-AV RDS) — both of which involve EBS. Numero uno One of those pieces in my immediate reach was a MySQL server, which we use to keep sessions. And to say the least about AWS and in their defense, the instance had run for almost 550 days and had never given us much or any reason to let us down....

So the other day, I wanted to quickly check something in BigCouch and thanks to Vagrant, chef(-solo) and a couple cookbooks — courtesy of Cloudant — this was exceptionally easy. As a matter of fact, I had BigCouch running and setup within literally minutes. Here’s how. Requirements You’ll need git, Ruby, gems and Vagrant (along with Virtualbox) installed. If you need help with those items, I suggest you check out my previous blog post called Getting the most out of Chef with Scalarium and vagrant....

A couple months ago, I wrote an article titled Operation CouchDB. I noticed that a lot of people still visit my blog for this particular post, so this is an update to the situation. And no, you may not copy and paste this or any other of my blog posts unless you ask me. ;-) Caching revisited A while back I wrote about how caching is trivial with CouchDB — well sort of....