A review of a 2008 research paper that proposed building a relational database on Amazon S3, using SQS as a write-ahead log and S3 as a page store. The design pioneered the storage-compute separation philosophy now central to cloud-native databases like Aurora, Snowflake, and Delta Lake. Key challenges included SQS's non-FIFO
Table of contents
SQS as WAL and S3 as PagestoreSurviving SQS and building B-link Trees on S3Isolation guaranteesConclusionSort: