A lot of popular websites wouldn’t be able to function without a NoSQL database on the backend. I mean, using a relational database for something like a social network is like putting a Clydesdale in the Kentucky Derby. Don’t get me wrong — Clydesdales are an excellent breed and probably the best at hauling carts — but my money’s on Seabiscuit.

NoSQL databases have been gaining popularity since 2009. Facebook, Twitter, Buzzfeed, Expedia, eBay, craigslist, and Google all use them. (If Google gave its blessing, it must be good, right?)

Relational databases are designed for static schemas and consistent, reliable transactions. They are not designed to handle booming data volumes at top speed. A NoSQL approach is often preferred for:

✓ Real-time data collection.
✓ Big data storage. NoSQL database structures include key-value pairs (simple and fast), documents (store info as XML/JSON), columns (good for queries), and graphs (good for networks), among others.
✓ Agile schemas. You don’t need to define a structure and stick to it. This can change on the fly.
✓ Horizontal scaling. It’s easy to scale out your architecture when you need to.
✓ Access via APIs. NoSQL uses object-oriented programming as opposed to SQL queries.
✓ Searchable catalogues of information — text, metadata, GIS, or otherwise.
✓ Developing a mobile app or an Internet of Things device.
✓ More: Check out this guy’s list of things people use NoSQL for.

This JSON snippet of a real-time bus location from the TransLink API would do well in a NoSQL setup.

This JSON snippet of a real-time bus location from the TransLink API would do well in a NoSQL setup.

Hundreds of NoSQL DBMS options are available and it’s worth researching which data structures and requirements are best for your scenario. A few choices, in order of current popularity:

Problems with going NoSQL

If you need to integrate a NoSQL database into your existing systems, there are some challenges involved. For example:

The above JSON from the TransLink API converted to point geometries and seen on a map.

Making it spatial: The above JSON from the TransLink API, converted to point geometries and seen on a map.

Using automation

The trick is to understand how NoSQL systems store data. Often, adopting NoSQL is a matter of converting your data to JSON and then loading it to the destination system.

Data to JSON to NoSQL

Many NoSQL DBMSs have some level of built-in import/export tools. However, their format support is limited, and writing XML/JSON means coding.

Coding aside, the only way to switch to a NoSQL system is via software solutions. By using an automated process, you’re also enabling loading/updating at regular intervals (or in response to a trigger). This means your data store can be updated in real time. For example, you could automatically capture data from web and mobile sources and move it into your NoSQL system without touching a thing.

Webinar

We have a webinar on how to integrate a NoSQL database with your existing systems (without writing any code!). We go through real demos and show you how to automatically merge a wide variety of data, extract data from NoSQL, and work with raw JSON.

Watch: Tips for Adopting NoSQL Databases using FME

Watch: How FME helps you switch to NoSQL

FME is great at processing JSON and has specialized writers for many database systems. Building a workflow to synchronize data with your NoSQL system is a drag-and-drop process, one that you can automate in real time.

Learn more about building your own NoSQL integration workflow, and try FME for free.

About Data Azure Bigquery Cloud Cloudant Couchdb Databases Documentdb DynamoDB Elasticsearch JSON Mongodb Nosql XML

Tiana Warner

Tiana is a product marketing manager at Safe Software. Her background in computer programming and creative hobbies led her to be one of the main producers of creative content for Safe Software. Tiana spends her free time writing fantasy novels and riding her horse, Bailey.

Comments

One response to “When (and How) to Switch to NoSQL”

  1. Akmal Chaudhri says:

    I have been tracking NoSQL databases since early 2012, collecting publicly available data on skills and vendors. The NoSQL market is still tiny. Considerations and summary of data in Section 2 of this very large slide deck: https://speakerdeck.com/abchaudhri/considerations-for-using-nosql-technology-on-your-next-it-project-1 Slides regularly updated with new data as I find it. Data last updated in August 2016.

Leave a Reply

Your email address will not be published. Required fields are marked *

Related Posts