Polyglot persistence: All content tagged as Polyglot persistence in NoSQL databases and polyglot persistence
After learning about LinkedIn’s Databus low latency data transfer system, I’ve had a short chat with Sid Anand focused on understanding what makes Databus unique.
As I’ve mentioned in my post about Databus, Databus looks at first as a data-oriented ESB. But what is innovative about Databus comes from decoupling the data source from the consumers/clients thus being able to offer speed to a large number of subscribers that are up-to-date, but also help clients that fall behind or are just bootstrapping without adding load on the source database.
Databus clients are smart enough to:
- ask for Consolidated Deltas since time T if they fall behind
- ask for a Consistent Snapshot and then for a Consolidated Delta if they bootstrap
and Databus is build so it can serve both Consolidate Deltas and Consistent Snapshots without any impact on the original data source.
The “catching-up” and boostrapping processes are described in much more details in Sid Anand’s article.
Databus is the single and only way that data is replicated from LinkedIn’s databases to search indexes, the graph, Memcached, Voldemort, etc.
Original title and link: What Is Unique About LinkedIn’s Databus ( ©myNoSQL)
Marting Fowler and Pramod Sadalage in an infographic promoting their upcoming book (PDF):
Polyglot persistence will occur over the enterprise as different applications use different data storage technologies. It will also occur within a single application as different parts of an application’s data store have different access characteristics.
There are over 2 years since I’ve begun evangelizing polyglot persistence. By now, most thought leaders agree it is the future. Next on my agenda is having the top relational vendors sign off too. Actually, I’m almost there: Oracle is promoting an Oracle NoSQL Database and Microsoft is offering both relational and non-relational solutions with Azure. They just need to say it.
Original title and link: The Future is Polyglot Persistence ( ©myNoSQL)
No 2012 predictions. Just facts.
GigaOm’s Barb Darrow commenting on Oracle’s Q2 financial results:
This is bad news for the company which pinned its cloud hopes on specialized data center appliances — the Exadata database machine, Exalogic middleware/application appliance, Exalytics analytics engine as well as a proposed ”Big Data Appliance.” This is the third consecutive quarter where Oracle posted hardware sales declines but this is probably more painful because the company is finally now fully engaged in its big data center appliance push.
As a low to mid range customer, I was disenfranchised by oracle, and we have gotten rid of segments of oracle in our data center. Just recently they have shown interest in us again so perhaps the low margin equipment will be back. Sun was not focused enough, and Oracle was too focused. Hopefully they are finding an profitable and useful middle ground.
So, NoSQL database #9999 there are many other equally usable solutions that are far more transparent in the way they do business and foster community around their products. This isn’t about paying money. This is about trust. So, sorry NoSQL #9999, but I’ll not be entering your sales cycle in this fashion or evaluating your product at this time. Moving along now…
Original title and link: How Polyglot Persistence and Having Data Storage Options Changes Things ( ©myNoSQL)
The architecture of the future based on polyglot persistence:
From Brad Anderson’s Introduction to NoSQL presentation:
Original title and link: Polyglot Persistence: The Architecture of the Future (NoSQL databases © myNoSQL)