# Future-Proofing

PuffinDB is designed to take advantage of the very latest serverless technologies (*Cf.* [Architecture](Serverless.md)), and what is likely to come next:

- Serverless containers ([AWS Fargates](https://aws.amazon.com/fargate/)) that could start in 15s instead of 60 to 90s
- Serverless functions ([AWS Lambda](https://aws.amazon.com/lambda/)) that could "officially" be used in a stateful manner
- Serverless functions that could be provisioned in very large numbers (hundreds of thousands)
- Serverless containers and functions that could be instantiated in larger numbers (thousands and tens of thousands respectively)
- Serverless containers and functions with 2 to 4 times more vCPUs and memory
- Serverless containers and functions with 2 to 4 times higher bandwidth/memory ratio
- Serverless containers and functions with GPU support.
- Serverless containers and functions with superchip support ([NVIDIA Grace Hopper](https://www.nvidia.com/en-us/data-center/grace-hopper-superchip/))
- Serverless [Redis](https://redis.io/) cluster ([Amazon ElastiCache for Redis](https://aws.amazon.com/elasticache/redis/), but serverless)
- SSD tier for Object Store ([Amazon S3](https://aws.amazon.com/s3/))
- In-memory tier for Object Store ([Amazon S3](https://aws.amazon.com/s3/))
- [Parquet](https://parquet.apache.org/) export when using [`SelectObjectContent`](https://docs.aws.amazon.com/AmazonS3/latest/API/API_SelectObjectContent.html)
- [DuckDB](https://duckdb.org/) embedded within Object Store (as an upgrade from [`SelectObjectContent`](https://docs.aws.amazon.com/AmazonS3/latest/API/API_SelectObjectContent.html))
- Object updates in place within Object Store (powered by file formats that support them, such as DuckDB's native file format)
- [SQL Superchips](https://twitter.com/ghalimi/status/1621904627334791170)

We look forward to working with [AWS](https://aws.amazon.com/) and other cloud providers to make these wishes come true.
