The problem with NoSQL databases

NoSQL databases, whether they are truly “no SQL” or “not only SQL,” defer differ from relational databases in one major respect; they tend to be easier to work with, and are better suited for use with real-time Web applications.

That’s why major and minor technology outfits are throwing development effort in the NoSQL field.

In the Free Software community, most people working with relational databases only have to contend with either MySQL (now increasingly MariaDB) or PostgreSQL or sometimes even SQLite. However, in the NoSQL arena, there are dozens of options to choose from.

Whether you want to use a Key-value or a document store NoSQL database, the most difficult task might be deciding which one to choose from a very long list of good options. Should it be MongDB MongoDB, Couchbase, CouchDB, Hypertable, HyperDex, Riak, Redis, DynamoDB, SchemafreeDB, or any other from this list or this one. Oracle has even jumped into the fray with Oracle NoSQL.

No matter your choice, this is one thing you gotta know. These databases can be resource intensive. They demand higher CPU and RAM allocation than any relational database. For example, when installing Couchbase, you are informed that you need a system with 4 CPUs and 4 GB of RAM. It will run on less, but when your website gets a traffic boost, be prepared to allocate more resources in a hurry.

And that’s the problem with these NoSQL databases. And that’s the reason most shared Web hosting companies will not offer them to you on a shared hosting account. You need a Cloud or VPS or a dedicated server. I experienced that first-hand when I was trying to use LampCMS to run a question and answer forum. The fact that the developer chose MongoDB as the database to use meant that using it on my shared hosting account was out of the question. And even when I migrated to a VPS service, using the basic VPS package was not going to do it.

Ultimately, using a NoSQL database will have an impact on the adoption of Free Software Web applications that use such a database. If you are trying to develop a Web application, that’s something to think about.

Related Posts

Administrations sponsor extension of open source network monitoring tool Several public administrations in Spain are sponsoring the development of Zorb, an open source extension to Nagios, an open source network monitoring ...
These reCAPTCHAs where not meant to be read by humans A reCAPTCHA is supposed to make business tough for bots yet easy for humans to decipher. But we all know how annoying those things can be - for humans...
This is not just about your personal privacy Aside from revealing the names of specific programs that the government has been using to violate the privacy of all and sundry, to most people who ha...
Know who’s tracking your e-reading habits The holiday shopping season is upon us, and once again e-book readers promise to be a very popular gift. Last year's holiday season saw ownership of a...
Another one bites the dust, and goes open source According to an old saying, when the going gets tough, the tough gets going. That, however, does not seem to apply in the proprietary software busines...
WebRTC voice and video now available on Firefox Nightly, but… WebRTC voice and video is now available on Firefox Nightly. That's the latest news from the Mozilla Foundation and TokBox, the Web communications comp...

We Recommend These Vendors

Launch an SSD VPS in Europe, USA, Asia & Australia on Vultr's KVM-based Cloud platform starting at $5:00/month (15 GB SSD, 768 MB of RAM).

Deploy an SSD Cloud server in 55 seconds on DigitalOcean. Built for developers and starting at $5:00/month (20 GB SSD, 512 MB of RAM).


6 Comments

  1. ‘MongDB’ lol…

  2. Concerned

    It would be nice if you ciuld use proper spelling, i.e. “differ” as opposed to “defer”.

    As a blogger, I expect not pertinent information, but proper spelling, punctuation, etc… You shiuld be able to present your information without butchering the language.

    • Concerned

      Sorry, meant to say “not only pertinent”.

    • Thanks for the correction. That seems to happen everywhere. I spot similar grammar errors myself on other blogs and try to read and re-read before clicking the Publish button, but still manage to miss something like the one you found.

      By the way, it’s not that I don’t know the difference, just that, well… errors happen.

      Talking about “proper spelling” and “butchering,” is your misspelling of could and should by design or did you just commit butcherings of your own?

      • Concerned

        It was a butchering of my own since this was sent from my phine (sorry “phone”, darn those tiny keyboards and fat fingers!).

Leave a Comment

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

*