Cloudant Supports CommonJS and new DB core releases

By Adam Kocoloski

At Cloudant, we’re improving our service and pushing out updates all the time. But we’re not always the best at letting you know about the newest features to take advantage of. In the months ahead, it’s my goal to keep you better informed.

2012 was a big year for us, and we wanted to kick off 2013 the right way: we’ve already deployed five dbcore releases in the last two months (934, 983, 1023, 1120, 1133). We hope you like what we’ve done with them. Here are a few new features I’m particularly excited about:

CommonJS support

This week we delivered CommonJS support to all multi-tenant clusters. It’s been one of the most widely requested Cloudant features, especially among customers from the CouchDB community. We’re pleased to make it available.

Validate JavaScript in views before accepting an upload (dbcore 1023)

It should no longer be possible to save MapReduce view code that fails to compile. Instead, users will receive a polite message informing them which of the map or reduce functions in their design document failed to compile and why. We will extend validation to all server-side JavaScript soon, but MapReduce views are the logical place to start.

Regular request pattern for replicator (dbcore 1120)

We’ve changed the Cloudant replicator to use a different set of query options that will more cleanly disconnect TCP connections. It’s a better way to run event feeds that’s friendlier to our ops team, making continuous replications more debuggable and stable over the long term. But what does this mean for you?

As we near the merger of Cloudant’s BigCouch fork into the next official release of Apache CouchDB, it means that Cloudant’s work fine-tuning its replicator will inform CouchDB’s own forthcoming replicator. At Cloudant, we’ve seen CouchDB running at massive scale supporting all sorts of different workloads. Since horizontal scalability is one of the goals of the BigCouch-Apache merger, we’ve learned that that a better replicator will go a long way toward helping people work better at bigger scale, whether you’re on Cloudant or not.

Better handling of attachments (dbcore 934)

Slow client readers and idle connections -- common in mobile applications -- are now more reliably handled on Cloudant. Previously in such scenarios, attachments larger than a few MBs could time out, even when there was still data on the socket. Not anymore. We fixed timeouts related to slow attachment readers and large attachment uploads, paving the way for a smoother TouchDB experience on Cloudant.

Let us know what you think and what new features you’d like to see in coming releases.

See you soon for the next dbcore release!

--Adam Kocoloski, CTO, Cloudant

Sign Up for Updates!

Recent Posts