Multi-tenanted streams @Workday
summary
Workday must never store or transmit two tenants’ data with the same encryption key while streaming large volumes (39+ million workers, hundreds of millions of messages/week across six jobs and six data centers). The team extends Avro with a hook to perform encryption-at-serialization, generates tenant-marked POJOs so objects carry tenant context, and uses a shared security library to fetch per-tenant keys and encrypt/decrypt during serialize/deserialize. This runs in production; remaining gaps: S3/Hadoop edge cases, heavy key-rotation for long-term state, and OpenStack operator tooling.
AI-written summary · about
chapters (5)
- 0:00Workday and Flink overview
- 6:12Multi-tenancy challenges
- 10:30Implementation of encryption
- 23:07Operational challenges
- 29:18Q&A and closing
related talks
45mDeep Dive into Data Streaming Security
20mSecuring workloads using data protection services
45mData Privacy for SaaS Kafka or Pulsar Offerings
56mDeep dive into data streaming security
50mBuilding Production-Grade End to End Encrypted App...
21mWorkday's Multi-Cloud Network Fabric With Consul & Vault
21mDedicated Infrastructure in a Multitenant World
38mDelivering Enterprise-Grade Object Storage: Bloomberg’s IAM Journey in a Multi-Tenant Arch...