IBM introduces Cloudant for Transaction Engine

IBM introduces Cloudant for Transaction Engine

This week, the team at IBM announced that they are enabling Cloudant, an elastically scalable, serverless datastore for Transaction Engine

Introduced in 2014, this Apache backed database service has delivered scalability and availability while sacrificing some of the consistency and isolation guarantees of traditional relational database systems. By equipping Cloudant on Transaction Engine, the team is restoring them within the serverless, scalable environment.

IBM has also announced an ecosystem of partners that includes DataStax Enterprise, EDG and MongoDB for enabling IBM to enrich the database capabilities available on cloud with the latest innovations, enterprise capabilities, and authentic technology from the vendors themselves. 

What’s new about Cloudant?

Efficient Storage and Scalability

The new update gives major relief to the developers as the Cloudant instances running on the Transaction Engine now supports databases up to 100TB. Also the per-gigabyte storage pricing for these new instances has been reduced by 4x [1]. 

Data Security 

Cloudant on Transaction Engine implements native database encryption to make sure that the user data be represented as ciphertext before it hits the disk. The database is kept secured as it is encrypted with a unique Data Encryption Key without any additional cost and is traced back to IBM Cloud’s standard key management services.

Open by design 

Cloudant on Transaction Engine is integrated with the open source Apache CouchDB. The core database features powering the instances are being developed as part of the next release of Apache CouchDB

Adam Kocoloski, IBM Fellow & VP, Cloud Databases, writes, “While we firmly believe that Cloudant provides the best vehicle for clients to benefit from these innovations, we are committed to the principle that you own your data, and we will always support an open API and replication interoperability with the open source community.”  


Leave a Reply

Your email address will not be published. Required fields are marked *