Is MongoDB Trending

More and more users are using MongoDB as the need for unstructured data usage is rising. As you know most of our data is unstructured and further, the growth of unstructured data is in exponential growth as shown below. 

MongoDB trends were analysed by  3T Software Labs with 18,000 professionals and it is shown that MongoDB is promising among data professional. However, you need to be little careful as 3T Software Labs is a company who is making MongoDB client tools. So this data can be little bias towards to the MongoDB anyway.

However, let us look at some of their findings. 

 

First, let us look at the MongoDB usages. 

This figure shows that over last three years, more and more usage of MongoDB towards large volume of data in 2020 Mongdb is used in 9.3 % in over 1 TB usage of database which is a huge growth from 2017 which is 2.8%.

According to the above figure, usage of Redis has a significant growth which organisations that use only MongoDB is groped to 37% from 46%. This is due to fact that most organization now do not believe in one database god. They use different horses for different causes. 

In the db-ranking MongoDB is ranked high over its counterpart as shown below. 

All of these data show that MongoDB is trending database in the industry.

What is the Best Database

If someone asks you "What is the best database", what is your answer. Answers might be different depending on your job role, whether you are a developer or a database administrator or client.

However, there is a ranking done for the database every month and the following is the latest ranking of databases. 

You can look at the rank of all the 359 databases here. According to this ranking, first six databases, Oracle, MySQL, Microsoft SQL Server, PostgreSQL, MongoDB, IBM BD2 are remaining the same compare to the last year.  If you look at the entire list you will find that Azure SQL Server Database is a major improvement. Azure SQL Server Database ranked 17 this year where it was 25th in last year.  

Let us look at the trending of these databases. 

You can see that MySQL and Oracle are running closers whereas PostgreSQL and MongoDB are running a close encounter. 

This does not say one database is better than others. This ranking based on various factors, such as Number of mentions of the system on websites, Frequency of technical discussions about the system, Number of job offers, in which the system is mentioned, Number of profiles in professional networks, in which the system is mentioned, and Relevance in social networks etc. You can look at the complete ranking parameters here.

The World According to DBAs

Database administrators (DBAs) are at the frontline of data management in most enterprises, identifying and often choosing to adopt new technologies. According to a new survey of DBAs, "While Hadoop and NoSQL are exciting new technologies," primarily large companies use them now and they "do not factor into many companies' plans over the next few years." Furthermore, traditional database management systems remain the foundation for information management infrastructure in most organizations, with Oracle and Microsoft SQL Server the dominant platforms for supporting mission-critical data. To examine the database infrastructure, understand the roles of DBAs today and how their roles are changing, Dell commissioned Unisphere Research, a division of Information Today, to survey database administrators and others charged with managing corporate data. There were 300 respondents from a wide range of companies representing a dozen industries. Two-thirds came from organizations with more than 1,000 employees. One-quarter of respondents' organizations run more than 500 databases. - See more at: http://www.cioinsight.com/it-strategy/big-data/slideshows/the-world-according-to-dbas.html#sthash.9u6JjSqn.dpuf

NoSQL and Related systems by feature

I got this from datascience course in www,coursera.org

EC – > Eventual Consistency

CREATE INDEX vs ENSURE INDEX

When creating an INDEX in many database systems we use, CREATE INDEX statement. However, in MongoDB command is ensureIndex. Reason for this is, ensureIndex will ensure there is an index on given attribute. CREATE INDEX will create an index on given columns for given index name.

Also, if you execute CREATE INDEX twice second execution will fail. However, in ensureIndex multiple execution will not fail.

MongoDB 2.4 Feature Demo and Q&A on Geo Capabilities

 

Watch Webinar on Geo Capabilities of MongoDB

Search in MongoDB

I came across this incidents while working on some MongoDB. I am not sure it is the expected behavior, so thought of posting it.

I have a collection called zipcodes which has following attributes.

So, I need to get the count for two state , I executed following script.

it returned me  1596 which was incorrect. Then started to go more into details, I started with by interchanging the values and then I got a different results.

Then I remove first row and executed it again.

Oops, I got the same values as before. Then I realize that, whenever we pass values for same attribute only the last one will be taken in. So for the above case I should us $in.

This behavior is same for insert, update, find etc.

UI Features in RoboMongo

I posted about RoboMongo tool around one month back. Thought of writing about two UI features of the tool.

Intelli-sence

This tol provides the intellisense feature so that users have the option of selecting the command rather than typing it.

Query Formatting

When large queries are typed, it will format the queries with different colors as shown below.

Reduce Dev Time and Improve Performance with MongoDB Training

Learning best practices for MongoDB development and administration can help reduce development time for your application, and increase reliability and performance. Get yourself and your team up to speed quickly with 10gen's comprehensive courses in person and online:

• MongoDB for Developers: Learn best practices for document-based data moderling, queries and commands, map/reduce and basic administration.
• MongoDB for Administrators: Diagnose performance issues, import and export data from MongoDB and establish the proper backup and restore routines.

Why MongoDB doesn’t need Transactions and Constraints

Eye brows may be raised when we say MongoDB doesn’t support transactions and constraints. First let us look at why we need transactions and constraints in relational databases.

Let us think about a simple blog system in relational databases.

So in relational, one transaction need to be saved in three tables. So there can be a scenario where post will get updated and tags will not be updated.  To avoid this, you can run all the statements in a transaction.

Also, there can be another scenario where user can insert into tags without inserting into posts table. So the constraints are used to avoid such situations.

How are we saving this data in MongoDB.

So in MongoDB, tags and comments are embedded to the posts documents so that above scenarios will not exist. 

DROP and REMOVE Mongo documents

In MongoDB you have two options to remove all the documents in a collection.

db.users.drop ()

db.users.remove()

thought the output of above two statements ( removing the all the documents in a collection) is same, there are couple of differences with two options.

remove will remove document one by one where as drop will remove all the documents at once. So in case you are dropping documents of a large collation, drop will be much faster than the remove.

However, drop will remove the meta data related to the collection as well. for example, it will remove the indexes associated with the collection.

So if you want to remove all the documents in a large collection, better option is use drop statement and recreate indexes again.

Robomongo 0.6.8

Are you irritated by using command line to manage MongoDB, there is FREE tool named Robomongo.

You can download executable for windows and Mac from http://www.robomongo.org/ for free. According to the site, Linux version is coming.

From the left hand , you have the option of navigating to databases and collection.

Also, you can run the mongodb queries and retrieve the relevant data.

Apart from these option followings are the options you have. So , you can duplicate collection and manage Indexes and manage shards.

NoSQL Benchmarking

In this article it will reveal the characteristics of Cassandra, HBase and MongoDB identified through multiple workloads.

Webinars on MongoDB

Webinar: Best Practices for MongoDB on AWS

Thursday March 28th 11:00am PDT / 2:00pm EDT / 6:00pm UTC

In this session we will look at best practices for administering large MongoDB deployments in the cloud.

Click here for more information.

Webinar: How Telcos Use MongoDB

Tuesday April 2nd 7:00am PDT / 10:00am EDT / 2:00pm UTC

In this webinar, you will learn how operators are increasingly leveraging MongoDB to develop new applications quickly and secure new revenue streams.

Click here for more information.

Webinar: Deployment Best Practices

Tuesday April 9th 11:00am PDT / 2:00pm EDT / 6:00pm GMT

(We suggest registering at least 30 minutes before the start of the webinar.)

The last bugs are finished, testing is complete, and business is ready. What do you do next? In this talk we will cover the topics to ensure that you are prepared for a successful launch of your MongoDB based product, including:

Click here for more information.

Webinar: How Banks Use MongoDB as a Tick Database

Tuesday April 16th 7:00am PDT / 10:00am EDT / 2:00pm GMT

(We suggest registering at least 30 minutes before the start of the webinar.)

Click here for more information.

Webinar: MongoDB 2.4 Feature Demo and Q&A on Geo Capabilities

Thursday April 18th 11:00am PDT / 2:00pm EDT / 6:00pm UTC

In version 2.4, there have been significant enhancements to the geospatial indexing capabilities in MongoDB, such as polygon intersections, a more accurate spherical model, and better integration with MongoDB's aggregation framework.

Click here for more information.

Webinar: NoSQL as the New Normal

Tuesday April 23rd 11:00am PDT / 2:00pm EDT / 6:00pm GMT

What started as a way for web giants to solve problems of serious scale has become the default way all enterprises manage Big Data. Despite having a catchy, if inaccurate title, there really isn't a coherent "NoSQL" category, nor is there a simple future for the range of NoSQL databases. In this presentation, Matt Asay will outline the reasons for NoSQL's existence and persistence, how the different NoSQL technologies help enterprises get control of Big Data, and will identify the trends that point to a bright future for post-relational databases.

Click here for more information.

Webinar: MongoDB 2.4 Feature Demo and Q&A on Security

Thursday April 25th 11:00am PDT / 2:00pm EDT / 6:00pm UTC

In version 2.4, MongoDB Enterprise includes Kerberos support for integration into existing enterprise security systems, as well as role-based privileges to provide more granular security for your cluster.

Click here for more information.

Webinar: How Banks Manage Risk with MongoDB

Tuesday April 30th 8:00am PDT / 11:00am EDT / 3:00pm GMT

(We suggest registering at least 30 minutes before the start of the webinar.)

Click here for more information.

Webinar: MongoDB 2.4 Feature Demo and Q&A on Hash-based Sharding

Thursday May 2nd 11:00am PDT / 2:00pm EDT / 6:00pm UTC

In version 2.4, MongoDB introduces hash-based sharding, allowing the user to shard based on a randomized shard key to spread documents

Getting started with MongoDB

MongoDB is a famous representative of NoSQL databases. It is a document-oriented database, which means that data will be stored in documents. In this article it will see how to set up MongoDB for Windows and how you can get started with it.

This has C# and VB.net samples to create databases, create and access collection etc.

@Refresh Colombo

This was my first presentation in public outside Microsoft technologies. Presentation was on MongoDB which Susantha and myslef are doing quite a bit of R&D lately.

Our presentation went well and had few questions from the audience which was just over 1000.

Entire event was covered by adaderana

You can view all the pictures at facebook and samples are available in my skydrive.

MongoDB @Refresh Colombo

This is my first presetion on MongoDB in public. I did few presentation in office before this on same subject and written two articles to office Magazine. One of those articles won the best article award. So let's see how this will go @RefreshColombo

Multiple Query Plans

As my last post, this is again something I got from MongoDB.

Execution plans are vital to measure performance of your queries. How many times, you are puzzled with why that index is not using? why it is doing a scan?

In MongoDB, there is a option to view all the execution plans with query engine considered and what was used eventually.

syntax for that is db.users.find({UserID:14049}).explain(true)

explain() will tell you what is the query plan used and true parameter will give you all the query plans considered for the execution.

However, though this is a great feature to have, in case of SQL Server implementation may not be easy. In MongoDB anyway queries have one collection only and query plan is not complex

Dropping Duplicates

If you search for "Duplicate rows sql server", in Google you will get about 136,000 results. This will tell how series the problem is. I am not going to add another post to above huge number of articles. What I going to explain here is how some other database system does this.

I was able to attend to a MongoDB conference last month and came across few features which are nice to have features in SQL Server.

In MongoDB, there are few ways for creating indexes, one is stated below.

db.users.ensureIndex({UserID:1},{"unique":true, "dropDups":true})

Just to tell you what the above script is, users is the "table" (Collection in MongoDB) and UserID is the "column" (Attribute in MongoDB") and ensureIndex is the command to create the index.

so, in this statement, unique:true will create a unique index BUT if there are duplicates records, it will retain only the first "record" ( Document in MongoDB" ) and others will be deleted because of the dropDups:true statment.

Now, this is very efficient way of deleting duplicates, but you need to pay more attention before issuing this command.