Our thoughts about database management plus the latest information about the ObjectRocket platform.
Free 30-Day Trial
Provision a Redis (500MB), MongoDB with MMAPv1 (up to 5GB), and/or Elasticsearch with Kibana (1GB RAM / 8GB Disk) instance and experience the ObjectRocket platform backed by Fanatical Support® free for your first 30 days.
The MongoDB command line utility, rs.remove(), is used to remove a member from a replica set. Prior to MongoDB version 3.0, the rs.remove() command would cause elections to occur. However, starting with version 3.0 this is no longer the case. From version 3.0 onwards, the rs.remove operation will not cause any elections. This is good news for several reasons.
With the newly released Sitecore 9.0, I started thinking about the overall direction of Sitecore through a data lens. The biggest announcement was around Sitecore xConnect™, a framework of APIs and services that allows users to integrate customer interaction data collected by Sitecore with customer data from almost any third-party system or channel.
Database administration is rapidly moving toward DBaaS. By automating and speeding up tasks ranging from analysis of big data to provisioning and scaling of cloud usage, DBaaS takes administration off the shoulders of IT staff. This makes it possible to work on other projects, such as the development and operation of new software.
Using MongoDB alongside Sitecore xDB allows for the real-time, centralized administration of customer interactions — the turn in your analytics that will put your company on the cutting edge of outreach while closely securing your data streams.
By: Derek Johnson Antonios Giannopoulos, Grant Killian
In an earlier post on this series we're calling ObjectRocket MongoDB Deep Dive for Sitecore, we explored the "replica set" vs "sharded cluster" topic. We shared that for our large Sitecore projects at ObjectRocket, we've found a good MongoDB shard key for Sitecore is _id:1 or _id:hashed. In this write-up, we'll dive further into the topic of shard keys for MongoDB used with Sitecore. You may want to review the first post in this series for more background.
This post outlines some discoveries related to Sitecore knowledge base 939840, an article that explains how to avoid timeouts related to saving contacts with a large number of interactions to the Sitecore Analytics database.
By: Antonios Giannopoulos Antonios Giannopoulos, Grant Killian
MongoDB is a technology that’s easy to overlook in a Sitecore implementation. Many people come to Sitecore already knowing SQL Server, and C# applications running on IIS are as familiar as well broken-in blue jeans. As Sitecore systems evolve, however, they move into interesting areas that are somewhat off the beaten path for the typical ASP.Net developer. One gets into areas like Solr, Redis, or – the focus of this write-up – MongoDB.
Best practice dictates that every database user should only be assigned a minimum set of privileges that on the one hand allows the user to fulfill their mission, and on the other hand minimises the impact of a security breach. For example: a database user used for reporting; it is not nessesary and doesn’t make sense to provide write access since read-only access is adequate.
As of version 3.2 MongoDB supports partial Indexes. A partial index only indexes the documents that meet a specified filter expression, before 3.2 the closest index type to partial was the sparse index. A sparse index only indexes documents where the index field(s) is not equal to null. The sparse index is a great tool to create smaller and higher performing indexes. Partial indexes bring more flexibility to the equation.
In this blog I'm going to show you how use Robomongo to connect to your ObjectRocket MongoDB. Robomongo is a cross-platform MongoDB manager that is available both a paid and an open source version. Check out the Robomongo download page to grab the latest free version.
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.
Recently, Parse announced they'd be retiring their service entirely on January 28th, 2017. While this comes as a bit of a shock to their own customers and the community as a whole, they're working to ensure that the transition off their platform is a simple process. We at ObjectRocket are doing the same to help any customer find a good home for their MongoDB data! In this post I'll outline how easy it is to move over to the ObjectRocket family and how we can help. Let's jump right in.
Your mobile app's data is hosted on Parse and you just found out that Parse is shutting down. Now what? In this post, I'll cover how ObjectRocket can help support your transition with a fully managed MongoDB solution.
Today we are happy to announce the wider availablity of our fully managed Encryption-at-Rest for ObjectRocket MongoDB in Virginia (IAD), Dallas (DFW), Chicago (ORD), and London (LON). This optional premium feature is availiable on versions 2.6 and 3.0 (mmap or WiredTiger) in both dedicated and shared plans.