This is a great example of how simplicity often wins in practice. Too many systems overcomplicate storage and retrieval, assuming every use case needs full indexing or ultra-low latency. In reality, for many workloads, treating S3 like a raw table and letting the engine handle the heavy lifting makes a lot of sense. Curious to see how it performs under high concurrency—any benchmarks on that yet?
This makes sense for large-scale deployments where cost control is paramount, but I wonder how it holds up in environments with unpredictable traffic patterns. Have you found any practical workarounds for the lag introduced by dynamic scaling? In my experience, the trade-off between cost efficiency and real-time performance isn’t always worth it.
