This was fast:

This week at Google I/O we are launching support for MongoLab‘s fifth cloud provider – Google Cloud Platform. You can now use MongoLab to provision and manage MongoDB deployments on Google Compute Engine (GCE)!

Good move for MongoLab and good win for MongoDB users. I’ve read a lot of good things about Google’s Cloud Platform.

Original title and link: MongoLab offers MongoDB on Google Cloud Platform (NoSQL database©myNoSQL)

via: http://blog.mongolab.com/2013/05/mongolab-now-supports-google-cloud-platform/

InformationWeek, in an article about MetLife migrating to MongoDB:

“We had 60 different teams working together as one group, and they were working nights and weekends not because they had to but because they were excited and wanted to,” says Gary Hoberman, MetLife’s senior VP and CIO of regional application development.

Just imagine how many nights and weekends and holidays these guys would put in if allowed to use an IDE. Like vim or emacs.

Original title and link: MetLife uses MongoDB (NoSQL database©myNoSQL)

via: http://www.informationweek.com/software/information-management/metlife-taps-nosql-for-customer-service/240154741?nomobile=1

Flavio Percoco describing some workaround OpenStack’s queing system is when using MongoDB’s TTL collections:

Even though it is a great feature, it wasn’t enough to cover Marconi’s needs since the later supports per message TTL. In order to cover this, one of the ideas was to implement something similar to Mongodb’s thread and have it running server-side but we didn’t want that for a couple of reasons: it needed a separated thread / process and it had a bigger impact in terms of performance.

This got me thinking it might be one of the (few) features missing from Redis.

✚ Redis supports timeouts for keys. Redis 2.6 brought the accuracy of expiring keys from 1 second to 1 millisecond.

✚ Redis has support for different data structures like lists, sets, and sorted sets. But it’s missing the combination of the two.

Original title and link: MongoDB’s TTL Collections in OpenStack’s Marconi queuing service (NoSQL database©myNoSQL)

via: http://blog.flaper87.org/post/517c3ea50f06d3497faffe5a/?buffer_share=d639c

Rick Copeland designs a MongoDB Pub/Sub system based on:

• MongoDB’s capped collections,
• tailable data-awaiting cursors,
• sequences (using find_and_modify()),
• a “poorly documented option” of capped collections: oplog_replay¹.

If you’ve been following this blog for any length of time, you know that my NoSQL database of choice is MongoDB. One thing that MongoDB isn’t known for, however, is building a publish / subscribe system. Redis, on the other hand, is known for having a high-bandwith, low-latency pub/sub protocol. One thing I’ve always wondered is whether I can build a similar system atop MongoDB’s capped collections, and if so, what the performance would be. Read on to find out how it turned out…

The solution is definitely ingenious and it could probably work for systems with not so many requirements for their pub/sub. It’s definitely a good excercise in combining some interesting features of MongoDB (I like the capped collections and the tailable data-awaiting cursors).

✚ I’m wondering if the behavior of the tailable data-awaiting cursors is the one of the non-blocking polls.

Original title and link: MongoDB Pub/Sub With Capped Collections (NoSQL database©myNoSQL)

via: http://blog.pythonisito.com/2013/04/mongodb-pubsub-with-capped-collections.html

Antoine Girbal about counts in MongoDB:

Doing counts in MongoDB has always been a slow operation even on an indexed field… until now. To do the count, it would iterate through every single element in the index and try to match the key, giving a response time of several seconds for just a million documents. It would be especially slow on values with high cardinality, meaning that the count is high.

A bug-fix and an optimization using MongoDB’s B-trees.

Original title and link: Counting in MongoDB Just Got Much Faster (NoSQL database©myNoSQL)

via: http://edgystuff.tumblr.com/post/47080433433/counting-in-mongodb-just-got-much-faster

Damien Katz has posted on GitHub a design document for the data structures, called rev trees, used to support conflict management in Couchbase. The doc also includes references to the way conflict resolution is done in CouchDB and also compares rev trees with the vector clocks.

When this happens [nb the edits are in conflict] Couchbase will store both edits, pick an interim winner (the same winner will be selected on all nodes) and “hide” the losing conflict(s) and mark the document as being in conflict so that it can found, using views and other searches, by an external agents who can potentially resolve the conflicts.

Original title and link: Conflict Resolution Using Rev Trees and a Comparison With Vector Clocks (NoSQL database©myNoSQL)

via: https://github.com/couchbaselabs/cbconflictmgmt/blob/master/revtrees.md

Adrien Mogenet about his expectations on MongoDB’s evolution:

I was a real fan of MongoDB in it’s early days, while all of the current solutions were just emerging. […] To be clear, I’m definitely not against MongoDB. I just wanted through this article to point out the fact that they roughly changed their directions and lead to a project that I could not follow anymore;

Breadth vs depth.

Original title and link: Is MongoDB Still on Course? (NoSQL database©myNoSQL)

via: http://www.borntosegfault.com/2013/03/is-mongodb-still-on-course.html

Jordan Novet for GigaOm annoucing another round of funding raised by MarkLogic:

On Wednesday, MarkLogic’s success was validated again, as the company announced a $25 million round of venture funding, bringing the total it has raised to $71.2 million. Sequoia Capital and Tenaya Capital led the round; CEO Gary Bloom and other MarkLogic executives also contributed.

✚ In 2010, MarkLogic made the first steps to join the NoSQL trends. Not very vigurous steps, but not shy either. Dave Kellogg (CEO of MarkLogic): We are NoSQL too

✚ As of this year, MarkLogic tries to position its product as NoSQL for enterprise. Price-wise, I have to agree.

✚ MarkLogic also tries a amore aggressive positioning in the NoSQL space: MarkLogic’s New (Aggressive) Voice

Original title and link: MarkLogic Raises $25M to Keep Up Enterprise NoSQL Pitch (NoSQL database©myNoSQL)

via: http://gigaom.com/2013/04/10/marklogic-nets-25m-to-keep-up-enterprise-nosql-pitch/

Interesting new direction of TokuDB pushing their storage engine based on Fractal Tree Indexes to MongoDB:

Running MongoDB with Fractal Tree Indexes (used today in the MySQL storage engine TokuDB) is fully transactional. Each statement is transactional. If an update is to modify ten rows, then either all rows are modified, or none are. Queries use multi-versioning concurrency control (MVCC) to return results from a snapshot of the system, thereby not being affected by write operations that may happen concurrently.

Original title and link: MongoDB Transactions With TokuDB’s Fractal Tree Indexes Engine (NoSQL database©myNoSQL)

via: http://www.tokutek.com/2013/04/mongodb-transactions-yes/#gsc.tab=0

Read the Hacker News thread about Coinbase.

Money is going missing. Transactions have been delayed for days and, in some cases, over a week. Even amounts already in BTC aren’t leaving the system.

The (snarky) comment is that Coinbase is a bank built on MongoDB.

Emin Gün Sirer

Original title and link: Does Anyone Know What’s Going on at Coinbase? - a Bank on MongoDB (NoSQL database©myNoSQL)

via: https://news.ycombinator.com/item?id=5427985