The security and access restrictions are pretty basic in nosql databases. Never run them on VPS / machines with a public IP, When using a nosql database you are left to rely on network and OS level security.
Basically keep your databases running on a internal firewalled network that accept connections only from certain trusted hosts.
2) Use a recent version of os with all known security patches applied , preferably something like a *nix server.
3) Never let the end user know what database you are using.
I am not sure about these, as I am not from the Ruby side. That said I am considering to talk with fibervolt.com / linode.com , to see if they can get this done for me.
NoSQL databases are very new , and the application I am planning to use it (MongoDB) can easily run in multiple terabytes a month, as of today I haven't come across anyone who has used it at that scale. Just FYI..so if this something mission critical, do your due diligence on taking the nosql approach.. I chose it because I had no other choice, as I cannot have a preset schema.
Maybe I'm a numbskull.. I found Scala pretty complex :) Just could not get to complete the 6th chapter of the staircase book... I've kind of given up on Scala.
Basically keep your databases running on a internal firewalled network that accept connections only from certain trusted hosts.
2) Use a recent version of os with all known security patches applied , preferably something like a *nix server.
3) Never let the end user know what database you are using.