Over a million developers have joined DZone.
{{announcement.body}}
{{announcement.title}}

Martin Fowler: The Future is not just NoSQL, it's Polyglot Persistence

DZone's Guide to

Martin Fowler: The Future is not just NoSQL, it's Polyglot Persistence

· Database Zone ·
Free Resource

Compliant Database DevOps and the role of DevSecOps DevOps is becoming the new normal in application development, and DevSecOps is now entering the picture. By balancing the desire to release code faster with the need for the same code to be secure, it addresses increasing demands for data privacy. But what about the database? How can databases be included in both DevOps and DevSecOps? What additional measures should be considered to achieve truly compliant database DevOps? This whitepaper provides a valuable insight. Get the whitepaper

The NoSQL v. SQL argument has been beaten (almost) to death, and now it's time to look forward to the foggy future of the data storage and access.  Martin Fowler and Pramod Sadalage have s recently released a slick infodeck tracing a simple history of databases, as well as their own prophecy of where databases are headed, namely Polyglot Persistence, or: "Using multiple data storage technologies, chosen based upon the way data is being used by individual applications."  Below are a couple of screenshots from the infodeck, as well as a link to the .pdf. 





Link to The future is: NoSQL Databases Polyglot Persistence

Compliant Database DevOps and the role of DevSecOps DevOps is becoming the new normal in application development, and DevSecOps is now entering the picture. By balancing the desire to release code faster with the need for the same code to be secure, it addresses increasing demands for data privacy. But what about the database? How can databases be included in both DevOps and DevSecOps? What additional measures should be considered to achieve truly compliant database DevOps? This whitepaper provides a valuable insight. Get the whitepaper

Topics:

Opinions expressed by DZone contributors are their own.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}