Given my current kick of learning and using more NoSQL approaches, I find the timing of Heroku’s growing NoSQL support most excellent! ..and Adam from Heroku has his say here.
The Take-aways are this:
- It’s about adding tools to the toolbelt, not taking away SQL
- Polyglot Persistence, which is to use multiple datastores in an app
- NoSQL is a great match for cloud services
- Heroku will continue to add NoSQL support, and continue their great support of Postgres as well
Adam also talks a little about what a datastore is and whether memcached qualifies as one.
I know we could get VPS hosting and setup Capistrano to deploy a rails app, but using Heroku takes a lot of friction out of deploying rails. It’s easy to scale up, and they have great support for plugging in things like exception and performance monitoring. If TimesheetToaster takes off, I know I’d be able to scale to meet demand on Heroku.