How do you design a database schema to handle high write volumes while maintaining read speed?
Mention indexing strategy, read/write splitting, database sharding, caching layers (Redis), and choosing between SQL vs NoSQL.
"For high-write scenarios, I minimize indices on write-heavy tables since indexing slows writes. I separate database reads and writes using a primary-replica replica model where writes go to the primary node and reads are distributed to replicas. I implement Redis caching for hot read paths, and shard the database horizontally based on a tenant ID if the scale exceeds a single instance."