|CockroachDB Adds GDPR Compliance|
|Written by Kay Ewbank|
|Friday, 06 April 2018|
CockroachDB 2.0 has been released with geo-partitioning features that keep data close to the customer, and support for JSON. The developers also say there are new benchmarks showing it can handle ten times more throughput than Amazon Aurora.
CockroachDB was launched last year as a distributed SQL database that is cloud native, offers horizontal scalability with no single points of failure. The headline improvement in version 2 is support for multi-active geo-replication for high availability with geo-partitioning to address data sovereignty compliance. CockroachDB 2 makes it simpler to build multi-regional data clusters.
A new feature called geo-partitioning lets developers say where data should be stored at the database, table, and row level. The developers say this keeps data close to customers, and should make it possible for companies to comply with data regulations like the General Data Protection Regulation (GDPR).
GDPR is a European Union regulation that comes into effect on 25 May 2018. It means companies storing personal data have greater accountability obligations, and have to take more care to restrict international data flows. It affects any company that holds or uses European personal data both inside and outside of Europe.
The second improvement to CockroachDB is support for JSON. You now get native support for storing, indexing, and querying JSON documents. JSON provides a means for developers to work with unstructured data but still need stronger data integrity guarantees than those of NoSQL systems.
One of the more interesting claims made for CockroachDB is that in a head-to-head test using the performance benchmark TPC-C, CockroachDB 2.0 scaled to 10x the maximum throughput achieved by Amazon Aurora. The company also says that read / write performance of CockroachDB 2.0 scales linearly, allowing it to grow beyond system like those offered by Oracle, Postgres, or MySQL.
Summer SALE Kindle 9.99 Paperback $10 off!!
or email your comment to: firstname.lastname@example.org
|Last Updated ( Friday, 06 April 2018 )|