As the Meteor framework developers celebrate reaching version 1.0, after quite a few years of development, with their International Meteor Day we thought Compose should join in marking their milestone.
Earlier this year Meteor embarked on a project to plug its server into MongoDB's Oplog so that it didn't have to keep polling the database for changes when there were two or more Meteor servers handling clients. The Oplog is used by MongoDB as the core of its replication strategy, a constant stream of change information being generated by the database. Of course, for users of hosted databases this did mean that you had to get access to the Oplog for any database.
We've always been a good place to take care of your MongoDB database for your Meteor applications and we were ready for Meteor with Oplog Access for Elastic Deployments and the new generation of Meteor applications. Our Elastic Deployments already replicated databases for availability and resiliance and the Oplog stream is valuable to many other applications so we had already been doing the work to unlock that power. With Meteor's update there was a web platform that could really make use of it.
If you want to know more about the oplog, we have a series of articles introducing it and how it works with Node.js, Ruby, Go and Java. Most relevant to Meteor is our article on how to use Compose's hosted MongoDB with Meteor and the Oplog.
Since the arrival of the Oplog support, the folks at Meteor have been working away on their platform, refining it, optimizing it and extending it. On the way to 1.0, they introduced new packaging formats, new deployment options and, for good measure integrated in Cordova-based mobile application support which you can develop and deploy from your desktop. We're pleased to see Meteor have reached version 1.0 and look forward to more developments with their database backend in the future – we'll be ready for them because that's what we do - production-ready, future-ready databases, for everyone.