Elasticsearch and OpenSearch are not truly serverless, but rather offer "serverless-ish" solutions that mask existing complexity with reduced management costs. Both tools have historical pain points related to management complexity and costs, which are still present despite their recent announcements about serverless capabilities. Generation 1 databases like Elasticsearch and OpenSearch rely on stateful architectures, while Generation 2 databases adopt a shared storage layer and serverless architecture but still hold state in compute. The proposed serverless Elasticsearch workaround relies on Amazon S3 for data storage, but underlying data representation and data architecture issues persist. In contrast, third-generation databases like ChaosSearch are designed to be truly serverless and stateless, decoupling storage from compute and providing independent and elastic scaling. These solutions offer improved cost/performance, scalability, and availability compared to first- and second-generation architectures.