heroku: All content tagged as heroku in NoSQL databases and polyglot persistence
Wednesday, 1 February 2012
Neo4j on Heroku: Building a Movie Recommendation Website for $0.00
Recently Max de Marzi has published sort of a getting started with Neo4j on Heroku guide. Here is how Max described it:
It takes a lot less effort to build a website these days than it used to. All it takes is a clever dwarf standing on the shoulders of the right giants. In a series of blog posts, I walk you through creating a movie recommendation website using Neo4j, Heroku, themoviedb.org, Processing.js, GroupLens, Marko Rodriguez and Michael Aufreiter. Free database, free hosting, free movie posters, free visualization, free dataset, free recommendation algorithm, just need to add a little code to bring them all together and BYOP (bring your own popcorn).
This will not get you a Netflix or Amazon like recommendation engine, but using a similar approach could definitely tell if Muhammad Ali is truly the greatest.
Original title and link: Neo4j on Heroku: Building a Movie Recommendation Website for $0.00 (©myNoSQL)
Thursday, 15 December 2011
Standalone Heroku Postgres’ Unanswered Question
While the offer is clear and valuable in itself:
- 99.99% uptime
- 99.999999999% (eleven nines) durability
- read-only asynchronous replicas
- database cloning
I’ve been reading all posts about the announcement looking for the answer to the most obvious question: why would you use Heroku’s Postgres service from outside the Heroku platform?
As far as I can tell:
- the network latency will be significant
- network partitions will occur (more often than having both you application and data in the same DC)
- transfer costs will be significant
So what is the answer?
Media coverage :
- DatabaseJournal: Salesforce Heroku Offers Standalone Cloud-Based PostgreSQL Database — DatabaseJournal.com
- InfoQ: Heroku Launches Postgres as a Standalone Service.
- ZDNet: Heroku launches cloud Postgres database | Cloud | ZDNet UK
- eWeek: Heroku Launches PostgreSQL Database-as-a-Service - Application Development - News & Reviews - eWeek.com
- PCWorld: Salesforce.com’s Heroku Launches Stand-alone Database Service | PCWorld Business Center
- Tools Journal: Heroku Launches PostgreSQL Database As A Service
- CloudBeat: Heroku debuts SQL database-as-a-service for developers | VentureBeat
- SiliconANGLE: Heroku Launches Standalone PostGres Database-as-a-Service | ServicesANGLE
- ReadWriteWeb: Heroku Launches PostgreSQL Standalone Service - ReadWriteCloud
- GigaOm: Heroku launches SQL Database-as-a-Service — Cloud Computing News
- ITProPortal: Heroku Announces PostgreSQL Database-as-a-Service for Developers | ITProPortal.com
Original title and link: Standalone Heroku Postgres’ Unanswered Question (©myNoSQL)
Sunday, 11 December 2011
NoSQL Screencasts: Neo4j for Ruby and Java People, Plus Data Modeling and Querying
Before the weekend is over, you could spend a bit of time experimenting with Neo4j. If you are a Ruby person then you’ve probably learned from the persistent graph structures with Ruby/Rails thread that Neo4j with JRuby is the way to go. In the first video Peter Neubauer demonstrates the process of building and deploying a Neo4j-enabled application on Heroku:
Tuesday, 20 July 2010
Heroku Encourages Polyglot Persistence
Heroku published an article preaching polyglot persistence through a Database-as-a-Service approach:
Database-as-as-service is one of the coming decade’s most promising business models. […] DaaS also goes hand-in-glove with polyglot persistence. Thanks to database services, you won’t need to learn how to sysadmin/DBA for every datastore you use – you can instead outsource that job to a service provider specializing in each database.
While it definitely sounds exciting to be able to use all these NoSQL databases , we should always keep in mind the cost of complexity even if DaaS will help alleviate some of the complexity of heterogeneous systems.
The article includes also some interesting use cases for a couple of NoSQL databases:
- Frequently-written, rarely read statistical data (for example, a web hit counter) should use an in-memory key/value store like Redis, or an update-in-place document store like MongoDB.
- Big Data (like weather stats or business analytics) will work best in a freeform, distributed db system like Hadoop.
- Binary assets (such as MP3s and PDFs) find a good home in a datastore that can serve directly to the user’s browser, like Amazon S3.
- Transient data (like web sessions, locks, or short-term stats) should be kept in a transient datastore like Memcache. (Traditionally we haven’t grouped memcached into the database family, but NoSQL has broadened our thinking on this subject.)
- If you need to be able to replicate your data set to multiple locations (such as syncing a music database between a web app and a mobile device), you’ll want the replication features of CouchDB.
- High availability apps, where minimizing downtime is critical, will find great utility in the automatically clustered, redundant setup of datastores like Casandra and Riak.
These are good examples, but you can find many more in our coverage of NoSQL uses cases and the per-product case studies: CouchDB case studies or MongoDB case studies, etc.
Heroku Encourages Polyglot Persistence originally posted on the NoSQL blog: myNoSQL
