Why Postgres wants NVMe on the hot path, and S3 everywhere else

Postgres wants to use NVMe for hot data storage due to its performance benefits, while using S3 for cold data storage due to its durability and cost-effectiveness. This approach aims to optimize database performance and storage costs. Engineers should consider separating hot and cold data storage to improve application efficiency. This strategy is particularly relevant for cloud-based applications. It's essential to weigh the trade-offs between performance, cost, and data durability when designing storage solutions.