Achieving compliance with data localization regulations can be prohibitively expensive (depending on how your database is architected). It's important to evaluate where compliance is worth the effort and where it's not.
Compliance with data localization laws is difficult and expensive. It’s particularly expensive with a monolithic DB. This blog outlines the yellow brick road towards compliance and flexibility for shifts in the data protection tectonic plates.
Cockroach CEO Spencer Kimball reads the tea leaves on the evolution of data protection laws, and what companies can do to prepare for the unknown.
This post covers what Data Subject Rights are and how they can affect GDPR compliance for your company.
A Q&A with CEO Spencer Kimball about what GDPR compliance means for companies and how the process can be made easier using CockroachDB.
Still working on GDPR compliance? CockroachDB might be able to help.
Geo-partitioning keeps user data close to the user, reducing latency and improving UX while archival-partitioning allows you to store data efficiently.
With geo-partitioning, you can control which nodes house data with row-level granularity, thereby reducing latency and improving user experience.
Guide Chief Architect's Guide to GDPR & Databases The GDPR (General Data Protection Regulation) is more than just a few customer notifications. It impacts the location, means, and structure of company's databases. This guide provides a view of GDPR's impact on databases with an eye specifically for Chief Architects and their considerations.Topics include: How your database can support GDPR compliance Tools to support GDPR compliance How to scale rapidly with GDPR compliance Get the guide in your inbox Thanks!
This guide covers strategies for companies to scale into the EU while enabling GDPR compliance.