Cassandra hard
When enabling Internode Encryption (SSL/TLS), what is the most significant performance optimization recommended for high-throughput production clusters?
- A Switching from standard JDK SSL to the OpenSSL (tcnative) provider via JNI, which uses native C libraries optimized for AES-NI hardware instructions.
- B Encrypting only the headers of the packets but not the payload.
- C Changing the replication factor to 1 to reduce the number of encrypted connections.
- D Running the database on a virtual machine instead of bare metal.
Answer: A. Switching from standard JDK SSL to the OpenSSL (tcnative) provider via JNI, which uses native C libraries optimized for AES-NI hardware instructions.
Java's default SSLEngine is notoriously slow for high-concurrency network tasks. By using Netty with `tcnative`, Cassandra can bypass the JVM's SSL layer and use the much faster native OpenSSL implementation, often reducing the CPU overhead of encryption by more than 50%.
One system design question a day, with spaced repetition so the ones you miss come back.
Get the appRelated questions
- In a Cassandra Keyspace, what does a 'Replication Factor of 3' specifically guarantee for your data redundancy?
- Unlike a Leader-Follower architecture (like MySQL or Redis), how does Cassandra maintain high availability within its node cluster?
- Cassandra Query Language (CQL) looks similar to SQL. What is a fundamental SQL feature that CQL does NOT support to ensure distributed performance?
- What is the critical architectural function of the 'Partition Key' in a Cassandra table?
- Apache Cassandra is fundamentally designed as which architectural category of NoSQL database?
- An extreme financial trading application requires 'Batch' sync for the Commit Log. What is the fundamental throughput limitation introduced by this setting?