As an alternative to the Web storage standard, IndexedDB can provide more storage capacity. Web storage has fixed limits per website, but IndexedDB limits are "usually quite large, if they exist at all".[5]
Web SQL Database was a prior API developed by Apple.[12] But Firefox refused to add support for it and argued against it becoming a standard because it would codify the quirks of SQLite.[13][14] It was thus deprecated in favor of IndexedDB.[15]
IndexedDB 1.0 became a W3C Recommendation on January 8, 2015.[16]IndexedDB 2.0 became a W3C Recommendation on January 30, 2018.[17][3]IndexedDB 3.0 was released as a First Public Working Draft on 11 March 2021 and remains as a Working Draft as of 3 December 2024[update].[18]
Performance
Because IndexedDB is running inside of the security sandbox of a browser, all operations have to go through various security layers which decreases the performance of IndexedDB. With IndexedDB 2.0 [17] the getAll() method was added which allows to improve performance on bulk read operations.
References
^ abcdWeb Applications Working Group (2021-03-11). Alabbas, Ali; Bell, Joshua (eds.). "Indexed Database API 3.0". W3C. W3C First Public Working Draft. Web Applications Working Group. Retrieved 2021-05-15.
^Web Applications Working Group (2021-03-11). Alabbas, Ali; Bell, Joshua (eds.). "Indexed Database API 3.0". W3C. Editor’s Draft. Web Applications Working Group. Retrieved 2021-05-15.
^ abWeb Applications Working Group (2018-01-30). Alabbas, Ali; Bell, Joshua (eds.). "Indexed Database API 2.0". W3C. W3C Recommendation. Web Applications Working Group. Retrieved 2021-05-16.