In this post, we’ll explain some of the most common MongoDB use cases we come across and different characteristics that are influencing these choices.
Creating consistently good customer experiences has become a key challenge for many organizations.
Today’s users, customers, clients, and buyers are notoriously impatient. They demand new experiences that engage and inspire; and they wanted them delivered at light speed. Because of these demands and expectations, applications and data stores have evolved in order to provide these types of “I want it now” experiences.
There are lots of definitions for scaling. Scaling could be defined as removing the scales from a fish. However, with databases, scaling refers to having the ability to expand to meet additional needs around storage/disk, RAM/memory, CPUs/compute cycles, networking, or other resources.
Beginning in version 3.2, MongoDB tracks usage statistics for every index. To access these statistics, MongoDB offers the $indexStats aggregation pipeline stage. For example, the following command will provide the index statistics for the collection “test.foo”:
db.foo.aggregate( [ { $indexStats: { } } ] )
We won’t describe the $indexStats output as there is plenty of documentation and many good articles out there that cover this topic.
It’s no secret that NoSQL databases have gained tremendous ground over relational databases in the last decade. A primary driver for this is the huge amount of data generated today from sources we never would have dreamed of two decades ago.
It’s no secret that data is the cornerstone to any successful marketing campaign today. Your carefully collected data—shepherded by your equally carefully selected database administrator (DBA)—is a treasure trove of business intelligence that serves up all sorts of invaluable nuggets of information about your customers that you can use to your advantage and theirs.
The buzzword of the era is “customer experience.” But, how can you create a consistent and positive multichannel experience for your customers? The easy answer is data. The slightly more complex answer is that data is great, but without properly managed databases, your customer experience won’t necessarily improve.
Upgrading from an older version of MongoDB can be painful. We get it. Your app is working, you don’t have the time or resources to upgrade even though you know you need to.
The ease of installing and running MongoDB can lead to neglect of basic database management. Then one day you’re getting frantic calls from a client or coworker about an application that’s crashed. Your current MongoDB setup couldn’t handle the increased usage and simply gave up.
Have you noticed that your app is slow? Are snapshots of your MongoDB instances trending in the wrong direction? Troubleshooting MongoDB isn’t always easy because there are often a combination of issues causing slow database response. One of the most common issues we see slowing down MongoDB stem from index issues.
Read on to learn how configuring, scaling, maintaining and securing Elasticsearch can drain technical resources, and how the fully managed ObjectRocket platform frees developers to code.
Read More