Exciting news about the arrival of Cloudant on Transaction Engine.
The IBM public cloud is built on a foundation of innovation in open source, leadership in security, and enterprise-grade infrastructure, all with the goal of enabling our clients to rapidly build new applications while reducing the complexity of managing those applications as they scale. Today we’re announcing a substantial new capability on this front with the arrival of Cloudant on Transaction Engine.
IBM Cloudant is an elastically scalable, serverless datastore built to meet the needs of cloud native application developers. Since 2014, it has powered a wide variety of internal and external applications in IBM Cloud. Like many original “NoSQL” solutions, Cloudant delivered scalability and availability by sacrificing some of the isolation and consistency guarantees of traditional relational database systems.
As we enter Chapter 2 of cloud, we’ve tasked ourselves with restoring those mission-critical properties while preserving and enhancing Cloudant’s cloud native character. Cloudant on Transaction Engine represents our first major step towards achieving those objectives.
Scaling to new heights
The new Transaction Engine architecture efficiently organizes data for rapid retrieval at scale, and we’re passing those efficiencies on to our clients. Cloudant instances running on the Transaction Engine can support databases up to 100TB, and we’ve reduced the per-gigabyte storage pricing for these new instances by 4x . We’ve worked diligently on an optimized hardware profile to drive down costs and leverage new innovations in storage technology to support this new pricing. Data is still stored in triplicate and replicated across IBM Cloud Availability Zones, and you only pay for the storage that you use.
Query processing also gets a major boost from the Transaction Engine design. Smarter organization of the data in secondary indexes enables us to efficiently scale query throughput without imposing partitioning restrictions on your application’s data model. Create views and secondary indexes on your entire database and query them with predictable, consistent performance as you scale.
At launch, we are increasing the cap on provisioned read throughput by 5x —and if you need more throughput, contact IBM Cloud Support. Cloudant on Transaction Engine also eliminates Global Queries as a separate category of provisioned throughput, resulting in cost savings of up to 20x  for certain types of queries.
API calls issued to Cloudant on Transaction Engine operate against consistent, isolated snapshots of your database. Document operations are fully Linearizable, and secondary indexes are kept transactionally consistent with the main database. The native change capture feed exported for every Cloudant database is also totally ordered, and the service will never replay previously observed events unless asked to by the client.
While we’ve become experts at designing applications that make the best use of eventually consistent systems and happily share that expertise with our clients, a data service that is immune to eventual consistency simply eliminates a whole class of issues that a developer otherwise has to consider. We’re delighted to offer this capability in IBM Cloudant and look forward to expanding the set of mission-critical applications that can leverage IBM Cloud as a result.
Organizations entrusting their data to cloud databases need to know that the data is stored securely and protected from improper use. Cloudant on Transaction Engine implements native database encryption so that user data is represented as ciphertext even before it hits the disk. Each database is encrypted with a unique Data Encryption Key at no additional cost, and the root of trust for those encryption keys always traces back to IBM Cloud’s standard key management services, which leverage some of the most secure commercially available encryption technology in the industry.
Open by design
Cloudant on Transaction Engine reinforces IBM’s commitment to open innovation—the core database features powering the Transaction Engine instances are being developed as part of the next major release of Apache CouchDB. 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. Moreover, our Extension for Apache CouchDB offering ensures you can get the support you need to deploy and manage CouchDB in your own data center or other hybrid cloud environments. Blending CouchDB and Cloudant gives you a unique ability to bring your data exactly where it’s needed around the globe.
Clients are recognizing the benefits of the updates being announced today. "As a long-time IBM Cloudant customer, we are excited to onboard the new Cloudant on Transaction Engine benefits into the PayRange mobile payment architecture,” said Prashant Kanhere, CTO, PayRange. “PayRange provides contactless payment methods for clients across hundreds of thousands of machines, and this capability is more important than ever these days. We are big users of Cloudant global queries and have high throughput requirements, and we are always looking for ways to optimize for performance, scalability, and cost. Cloudant on Transaction Engine provides capabilities to take our application in the right direction on all those fronts."
In addition to announcing new capabilities to IBM’s Cloudant on Transaction Engine, we’re also celebrating the 50-year anniversary of the relational model behind Structured Query Language (SQL). In June 1970, IBM researcher and computing pioneer Edgar Frank Codd published the seminal paper “A Relational Model of Data for Large Shared Data Banks,” describing the famous relational model that became the foundation of SQL.
Get started today
 Storage on Cloudant previously cost $1/GB of disk. Cloudant on Transaction Engine costs $.25/GB of disk (see https://cloud.ibm.com/catalog/services/cloudant for comparison).
 Self-service query (read) capacity maxes out at 5,000 reads/second for Cloudant on Transaction Engine. Previously, it maxed out at 500 queries/second on Cloudant. Every read request with strong consistency costs 2 reads/second. 2,500 reads/second with strong consistency is 5x more than the previous cap.
 Five queries/second previously $0.00685/hour With Cloudant on Transaction Engine, a query is charged as a read. All reads require a budget of 2 requests/second for strong consistency. Therefore 5 reads/second (queries) cost an end user $.000024/hr. This equates to an "up to" 28x difference. Full costing is determined by amount of rows scanned and data returned from a Cloudant on Transaction Engine "read".