We’re excited to announce that MongoDB 3.2 is now generally available on ObjectRocket and ready for you to deploy today! We’ve been hard at work testing and validating the latest major release, and after a lot of careful tracking of the community patches and stability improvements, we are ready to put our full endorsement behind MongoDB’s latest and greatest.
We're excited to announce that the ObjectRocket for MongoDB Beta is now available in the Heroku Elements Marketplace.
At ObjectRocket, our vision is to offer our products and support where our customers’ applications live. We’re excited to announce the availability of ObjectRocket Redis on the AWS infrastructure. This is the first of many services to come giving customers choice in who manages their data regardless of the cloud on which it lives.
So you have a MongoDB data set, and you need a place to host it! As you've discovered, we have an impressive list of features, but up until this point, many of them have only been available for sharded instances. Some of the key features include 3 data nodes per shard, SSL connection options, WiredTiger storage engine, encryption for data at rest, and vertical scaling of resources. But if sharding doesn't fit your workload, your data schema, or your data volume, then it can be awkward or impractical to force yourself to use a sharded instance, when a simple replica set is what you really need.
For this tutorial on the new Redis GEO commands, we’re going a bit out of the box. Normally you might expect to see a tutorial showing you how to match users with local resources such as restaurants or hotels. For this we’re going to track runners in a marathon. This will showcase some of the more dynamic things you can do with Redis’ Geo support.