PDX-based PII Encryption Migration Strategies

The addition of PII encryption to existing Geode services necessitates a migration process. Subsequent to the initial implementation and for enhanced overall security, some firms might also want to re-encrypt PII data with updated keys, which implies a similar migration process. The target data sets are often quite large—Geode users frequently load regions that include PII data with tens of millions, hundreds of millions, and sometimes even larger sets of individual entries. For such large data sets, migration performance is an important factor.

This white paper dives into some of the key challenges for executing Geode data migrations, with a focus on minimizing or eliminating related service downtime, and specifically targeting the PII Encryption use case.

Previous
Spring Session for Apache Geode/Pivotal GemFire 2.1.2.RELEASE
Spring Session for Apache Geode/Pivotal GemFire 2.1.2.RELEASE

It is my pleasure to announce Spring Session for Apache Geode and Pivotal GemFire (SSDG), 2.1.2.RELEASE (o...

Next
Spring Session for Apache Geode/Pivotal GemFire 2.0.6.RELEASE and 2.1.0.RELEASE Available!
Spring Session for Apache Geode/Pivotal GemFire 2.0.6.RELEASE and 2.1.0.RELEASE Available!

Good things come in pairs, so I am happy to announce the availability of Spring Session for Apache Geode &...

SpringOne Platform 2019

Learn More