RDBMS: All content tagged as RDBMS in NoSQL databases and polyglot persistence
scaling data systems in real life has humbled me. I would not dare to criticize an architecture that holds the social graphs of 750M and works
So if you feel like watching an action movie featuring A-class actors, Todd Hoff has summarized the whole conversation paraphrazing a comment about Lady Gaga:
You know, there’s a difference between not liking someone’s music and not recognizing their talent. If€ you can’t recognize the fact that Lady GaGa is, in fact, extremely talented in many ways, then you may want to try to look at her with less of a bias. There’s plenty of artists I can’t stand, but still respect their talent.
Even if you don’t like Lada Gaga’s schtick, that is a great performance. I get the feeling a lot SQL people don’t recognize the talent of NoSQL, whereas NoSQL people are generally use the best tool for the job types who have no problem with you using SQL if that works for you.
Original title and link: Is Nosql a Premature Optimization That’s Worse Than Death? Or the Lady Gaga of the Database World? ( ©myNoSQL)
VMWare’s Cloud Foundry has the potential to become the preferred PaaS solution. It bundles together a set of services that it took years for other PaaS providers (Google App Engine, Microsoft Azure) to offer. And it seems that Cloud Foundry has much less (or none at all) vendor lock in.
From a storage perspective, Cloud Foundry is encouraging polyglot persistence right from the start offering access to a relational database (MySQL), a super-fast smart key-value store (Redis), and a popular document database (MongoDB). The only bit missing is a graph database.
I think the first graph database to get there will see an immediate bump in its adoption.
Original title and link: Cloud Foundry, NoSQL Databases, and Polyglot Persistence (NoSQL databases © myNoSQL)
From Gavin Heavyside’s slides:
- Launch successful service
- Read saturation: add caching
- Write saturation: add hardware
- Queries slow down: denormalize
- Reads still too slow: prematerialise common queries, stop joining
- Writes too slow: drop secondary indexes and triggers