I am at peace with my cookies.
HN user
mbroberg
I'm a dork.
Example Jupyter notebook: https://github.com/ibm-cds-labs/seti_at_ibm/blob/master/note...
We didn't publish to Maven Central. It's not a library, but I guess we could publish there. Thanks for the suggestion.
Built on Lucene 4.6.1, yes.
Disclosure: I work for Cloudant. There are two libraries outlined in the blog:
Clouseau, in Scala: https://github.com/cloudant-labs/clouseau Dreyfus, in Erlang: https://github.com/cloudant-labs/dreyfus
It's a huge place, but I agree with ahoff, having come over along with the Cloudant acquisition. I feel pretty good about our little corner of IBM in CDS (cloud data services). It's not a bad place to end up if you're at a data management startup.
For an overview of the query syntax, see https://cloudant.com/blog/introducing-cloudant-query/
Note: I work for Cloudant.
Disclaimer: I work for the Cloudant folks.
Infographic traces a few of the NoSQL databases important to Cloudant: https://cloudant.com/wp-content/uploads/NoSQL-Family-Tree.pn...
(I work at Cloudant.)
An interview we did with https://twitter.com/lancecarlson and https://twitter.com/ebzovi on rewriting their ruby app to use Cloudant's JSON doc store service. Flexible schema, and user permissioning implemented as a CouchApp.
(I work for Cloudant.)
Here's the email that Cloudant's CTO sent to Apache CouchDB:
SUBJECT: Cloudant & IBM: Our Commitment to Apache CouchDB
Apache CouchDB means a great deal to me, and to Cloudant as a company. Cloudant and CouchDB have grown alongside each other over the past several years in one of the more authentic vendor/community collaborations I can think of in Apache history. Today marks the next step in Cloudant’s growth as we enter into a definitive agreement to become part of IBM.
What does this mean for CouchDB? I would not have agreed to this transaction if I had any concerns about Cloudant’s ability to continue its contributions and collaboration with Apache CouchDB. IBM has a strong track record in open source software and a productive relationship with Apache; in fact, IBM was instrumental in bringing CouchDB to the ASF many years ago. IBM is fully supportive of our efforts here, and I’m looking forward to bringing increased resources to bear in support of the project.
CouchDB has the potential to shape the future of distributed data management and computing. 2013 was a year of tremendous progress, as we doubled our committer base and shipped no fewer than eight releases. Already in 2014 we’ve seen amazing progress on long-standing initiatives to enhance the core of the system. The timing is right — in the market and for the community — to take the next big step forward. With your help, that is exactly what we will do.
Truly, the future of CouchDB is CouchDB.
Adam Kocoloski Co-Founder & CTO, Cloudant
So then does this mean that PostgreSQL is to SQL like CouchDB is to NoSQL?
We hear similar stories from the field here at Cloudant. Distributed databases, scaling clusters -- that's hard stuff. Nice to see such a thoughtful post.
Assuming I understand this correctly -- and I could be wrong -- but I don't think that the pump thing would work for this use case. I think it's used for other applications. In this scenario, it needs to be to a DB next to these small agents. So spinning up an Oracle instance for each isn't really viable. Also, the agents aren't necessarily in labs that have the nice Oracle deal that CERN central has.
I started taking Bob Sedgewick's class and like it so far. https://www.coursera.org/course/algs4partI
From https://blogs.apache.org/couchdb/entry/welcome_bigcouch via http://blogs.apache.org/couchdb/
THURSDAY JUL 25, 2013 Welcome BigCouch
Good news! Cloudant has announced the completion of the BigCouch merge. This is a huge step forward for CouchDB. So thank you to Cloudant, and thank you to the committers (particularly Robert Newson and Paul Davis) who slogged (and travelled the world to pair with each other) to make this happen.
What does this mean? Well, right now, the code is merged, but not released. So hold your clicks just a moment! Once the code has been tested, we will include it in one of our regular releases. (If you want to help us test, hop on to the dev@ mailing list!)
What’s new? The key accomplishment of the merged code is that BigCouch’s clustering capability, along with the rest of Cloudant’s other enhancements to CouchDB’s code base, will now be available in Apache CouchDB. This also includes improvements in compaction and replication speed, as well as boosts for high-concurrency access performance.
Painless replication has always been CouchDB's biggest feature. Now we get to take advantage of Cloudant’s experience running large distributed clusters in production for four years. With BigCouch merged in, CouchDB will be able to replicate data at a much larger scale.
But wait! That’s not all! Cloudant has decided to terminate their BigCouch fork of CouchDB, and instead focus future development on Apache CouchDB. This is excellent news for CouchDB, even more excellent news for the CouchDB community.
Here’s the original press release:
Cloudant Contributes Database Scalability and Fault-Tolerance Framework to Apache CouchDB™
And here are some highlights from the press:
Sofa, so good ... BigCouch relaxes into comfy Apache CouchDB (The Register)
Cloudant pitches one CouchDB for all (GigaOM)
Cloudant Merges BigCouch Into Apache CouchDB (eWeek)
Cloudant Breathes Life Into CouchDB - Merges BigCouch into Apache Project (CMSwire)
CouchDB Gets Cloudant's 'Super-Size Me' Scaling (InformationWeek)
Cloudant Merges BigCouch Code into Apache Open Source Database (The WHIR)
Cloudant Merges BigCouch Database into Open Source Apache CouchDB (The VAR Guy)
Cloudant merges distributed BigCouch code with Apache CouchDB (JAXenter)
Cloudant contributes database scalability and fault-tolerance framework to Apache CouchDB (SD Times)
P.S. Cloudant is also hosting a party at OSCON on July 25 to celebrate the news. (They’re booth #305 if you’re at the show.) And if all that wasn’t enough, stay tuned for news about a CouchDB conference that we should be announcing shortly…
Posted at 06:26PM Jul 25, 2013 by Noah in News | Comments[0] |