RDBMS: All content tagged as RDBMS in NoSQL databases and polyglot persistence
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
James Governor reporting from the HP CEO Leo Apotheker keynote at the HP Analyst Summit:
“traditional relational databases are becoming less and less relevant to the future stack”
Even if HP acquired the real-time analytics platform Vertica I haven’t heard of HP in the NoSQL space, so my first thought was this is just the usual attack on competitors.
But it could also express HP’s interest in getting into the NoSQL market. The games of speculations about HP’s acquisitions are open.
A panel discussion on NoSQL, NoSQL databases, and relational databases, featuring Salvatore Sanfilippo
, Lenz Grimmer
, Filipe David Borba Manana
, and a forth person from SAPO whose name I couldn’t spell:
I was reading ☞ this post by Mark Suster explaining the innovator’s dilemma, incumbent and new comers behavior in the market. And then I realized that it applies very well to the NoSQL databases market too:
Professor Clayton M.Christensen’s, author of The Innovator’s Dilemma, definition:
An innovation that is disruptive allows a whole new population of consumers access to a product or service that was historically only accessible to consumers with a lot of money or a lot of skill.
Mark Suster’s comment:
So the startups tend to focus on totally new customers. They try to capture people that didn’t buy the expensive stuff in the first place because they couldn’t afford it. Often the startups are actually serving a slightly different kind of customer or a slightly different market need. The thing about “disruptive” technology as I interpret it is NOT that it is a major breakthrough in performance or functionality as most people conceive it. It is often LESS performant. What is “disruptive” is that is also dramatically less expensive. And the providers take a much lower margin – they have nothing to lose, nothing to protect.
Except that NoSQL databases must help you protect your data. Otherwise pretty sound.