End-to-end encryption
End-to-end encryption is a communication security technique in which only the originating and intended receiving endpoints can decrypt protected content.
Real-World Cryptography
End-to-end encryption is a communication security technique in which only the communicating endpoints can decrypt the exchanged content.
- How it is used
- Secures communications among people across untrusted networks without making intermediary servers trusted message readers.
- How deep it goes
- Explains communication topology and trust bootstrapping through public-key examples, then surveys protocols without developing implementation details.
- Examples
- Uses server-relayed messaging, Alice’s encrypted file to Bob, email encryption, and modern messaging applications.
- What you can do after
- Evaluate messaging designs by separating endpoint encryption from server-link protection and checking how users authenticate public keys.
Read how Real-World Cryptography explains end-to-end encryption →
Kafka for Architects
End-to-end encryption is a communication design in which data is encrypted by the producer or sender and decrypted only by the intended consumer or recipient.
- How it is used
- Deploys E2EE when regulatory or architectural requirements demand protected Kafka data at rest.
- How deep it goes
- Explains producer–consumer flow, partition-key constraints, KMS needs, compatibility issues, and proxy alternatives without implementation code.
- Examples
- Uses client-side encryption diagrams and contrasts filesystem, cloud-storage, application, library, and proxy-based protection.
- What you can do after
- Operate/configure a Kafka E2EE design by selecting client or proxy handling, preserving partitioning, and integrating a KMS.
Read how Kafka for Architects explains end-to-end encryption →
Apache Kafka in Action
End-to-end encryption is encryption in which data is encrypted by the originating endpoint and decrypted only by the intended receiving endpoint, without readable intermediaries.
- How it is used
- Protects highly sensitive Kafka transmissions beyond the confidentiality provided by transport, storage, and access controls.
- How deep it goes
- Explains client-side placement, serializer flow, proxy limitations, key management, field-encryption limits, and compression effects.
- Examples
- Uses JSON serialization, encrypted byte arrays, Kafka Connect Kryptonite, Conduktor Proxy, Kroxylicious, and Vault as implementation references.
- What you can do after
- Build client-side message protection by wrapping Kafka serialization and deserialization with encryption and a managed key process.
Read how Apache Kafka in Action explains end-to-end encryption →
Related concepts
- cryptographic protocolcontrasts with · A cryptographic protocol is a defined sequence of cryptographic operations and message exchanges that provides security properties between communicating parties.
- platformused by · A platform is a foundational computing system, environment, or online service that provides capabilities or infrastructure for building, running, delivering, or interacting with applications and services.
- public-private key pairuses · A public-private key pair is a mathematically related public key and private key used together for asymmetric cryptographic operations.
- TLScontrasts with · Transport Layer Security (TLS) is a cryptographic protocol that protects network communications through confidentiality, integrity, and authentication of communicating endpoints.
- encryptionkind of · Encryption is the cryptographic transformation of readable data into ciphertext to conceal its contents, reversible through decryption with appropriate information.
- browseruses · A web browser is software that retrieves, interprets, and renders web resources, executes supported web content, and enables interaction with web pages and applications.
These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.