[DO] Add seat booking app tutorial (#17063)

* SQLite in Durable Objects docs:

- Add DO SQL class migration, API, pricing, limits, and changelog.
- Update DO glossary

* Update src/content/docs/durable-objects/api/transactional-storage-api.mdx

Co-authored-by: Kenton Varda <[email protected]>

* Update src/content/docs/durable-objects/api/transactional-storage-api.mdx

Co-authored-by: Kenton Varda <[email protected]>

* Update src/content/partials/durable-objects/durable-objects-sql.mdx

Co-authored-by: Kenton Varda <[email protected]>

* Update src/content/partials/workers/transactional_storage_api_pricing.mdx

Co-authored-by: Kenton Varda <[email protected]>

* Address initial feedback

- Rename "Transactional Storage API" to "Storage API"

* Document next(), toArray(), and one()

* Fix indentation, complete rename from Transactional Storage API to Storage API

* Fix code formatting

* Fix code formate

* Fix render link

* Clarify billing

* Fix redirect

* add seat booking tutorial

* feedback changes and links update

* remove old code

* update HTML code to handle WS link on deploy

* Resolving merge conflict part 2

* Correcting typo in changelog.

* fix category

* Update src/content/docs/durable-objects/tutorials/build-a-seat-booking-app/index.mdx

Co-authored-by: Vy Ton <[email protected]>

* Update src/content/docs/durable-objects/tutorials/build-a-seat-booking-app/index.mdx

Co-authored-by: Vy Ton <[email protected]>

* Update src/content/docs/durable-objects/tutorials/build-a-seat-booking-app/index.mdx

Co-authored-by: Vy Ton <[email protected]>

* update class name and add toArray method

---------

Co-authored-by: Vy Ton <[email protected]>
Co-authored-by: Kenton Varda <[email protected]>
Co-authored-by: Jun Lee <[email protected]>

Author: 4 people

src/content/changelogs/durable-objects.yaml

@@ -11,7 +11,7 @@ entries:
       An issue was identified with [alarms](/durable-objects/api/alarms/) in [beta Durable Object classes with a SQLite storage backend](/durable-objects/best-practices/access-durable-objects-storage/#sqlite-storage-backend). Alarms have been temporarily disabled for only SQLite-backed Durable Objects while a fix is implemented. Alarms in Durable Objects with default, key-value storage backend are unaffected and continue to operate.
 
   - publish_date: "2024-09-26"
-    title: (Beta) SQLite storage backend & SQL API availabe on new Durable Object classes 
+    title: (Beta) SQLite storage backend & SQL API available on new Durable Object classes
     description: |-
       The new beta version of Durable Objects is available where each Durable Object has a private, embedded SQLite database. When deploying a new Durable Object class, users can [opt-in to a SQLite storage backend](/durable-objects/best-practices/access-durable-objects-storage/#sqlite-storage-backend) in order to access new [SQL API](/durable-objects/api/storage-api/#sqlexec) and [point-in-time-recovery API](/durable-objects/api/storage-api/#point-in-time-recovery), part of Durable Objects Storage API.
 

src/content/docs/durable-objects/api/storage-api.mdx

@@ -332,4 +332,4 @@ The PITR API represents points in times using "bookmarks". A bookmark is a mostl
 ### Related resources
 
 * [Durable Objects: Easy, Fast, Correct – Choose Three](https://blog.cloudflare.com/durable-objects-easy-fast-correct-choose-three/).
-* [WebSockets API](/durable-objects/api/websockets/).
+* [WebSockets API](/durable-objects/api/websockets/).

src/content/docs/durable-objects/best-practices/access-durable-objects-storage.mdx

@@ -10,7 +10,7 @@ import { Render } from "~/components";
 
 Durable Objects are a powerful compute API that provides a compute with storage building block. Each Durable Object has its own private, transactional and strongly consistent storage. Durable Objects [Storage API](/durable-objects/api/storage-api/#methods) provides access to a Durable Object's attached storage.
 
-A Durable Object's [in-memory state](/durable-objects/reference/in-memory-state/) is preserved as long as the Durable Object is not evicted from memory. Inactive Durable Objects with no incoming request traffic can be evicted. There are normal operations like [code deployments](/workers/configuration/versions-and-deployments/) that trigger Durable Objects to restart and lose their in-memory state. For these reasons, you should use Storage API to persist state durably on disk that needs to survive eviction or restart of Durable Objects. 
+A Durable Object's [in-memory state](/durable-objects/reference/in-memory-state/) is preserved as long as the Durable Object is not evicted from memory. Inactive Durable Objects with no incoming request traffic can be evicted. There are normal operations like [code deployments](/workers/configuration/versions-and-deployments/) that trigger Durable Objects to restart and lose their in-memory state. For these reasons, you should use Storage API to persist state durably on disk that needs to survive eviction or restart of Durable Objects.
 
 ## Access storage
 

src/content/docs/durable-objects/get-started/walkthrough.mdx

@@ -71,15 +71,15 @@ Your `MyDurableObject` class will have a constructor with two parameters. The fi
 <Tabs> <TabItem label="JavaScript" icon="seti:javascript">
 
 ```js
-export class MyDurableObject {
+export class MyDurableObject extends DurableObject{
 	constructor(state, env) {}
 }
 ```
 
 </TabItem> <TabItem label="TypeScript" icon="seti:typescript">
 
 ```ts
-export class MyDurableObject {
+export class MyDurableObject extends DurableObject{
 	constructor(state: DurableObjectState, env: Env) {}
 }
 ```
@@ -93,7 +93,7 @@ Your file should now look like:
 <Tabs> <TabItem label="JavaScript" icon="seti:javascript">
 
 ```js
-export class MyDurableObject {
+export class MyDurableObject extends DurableObject{
 	constructor(state, env) {}
 
 	async fetch(request) {
@@ -105,7 +105,7 @@ export class MyDurableObject {
 </TabItem> <TabItem label="TypeScript" icon="seti:typescript">
 
 ```ts
-export class MyDurableObject {
+export class MyDurableObject extends DurableObject{
 	constructor(state: DurableObjectState, env: Env) {}
 
 	async fetch(request: Request) {
@@ -218,6 +218,24 @@ tag = "v1" # Should be unique for each entry
 new_classes = ["MyDurableObject"] # Array of new classes
 ```
 
+### 6.a Optional: Configure new Durable Object class for SQL storage
+
+:::note[SQLite in Durable Objects Beta]
+
+New beta version of Durable Objects is available where each Durable Object has a private, embedded SQLite database. SQL storage is opt-in during beta; otherwise, a Durable Object class has the standard, private key-value storage. Objects can access long-lived durable storage with the [Storage API](/durable-objects/api/storage-api/). 
+
+:::
+
+A Durable Object class can only have a single storage type, which cannot be changed after the Durable Object class is created.
+
+To configure SQL storage and API, replace `new_classes` with `new_sqlite_classes` in your Worker's `wrangler.toml` file:
+
+```toml
+[[migrations]]
+tag = "v1" # Should be unique for each entry
+new_sqlite_classes = ["MyDurableObject"] # Array of new classes
+```
+
 Refer to [Durable Objects migrations](/durable-objects/reference/durable-objects-migrations/) to learn more about the migration process.
 
 ## 7. Develop a Durable Object Worker locally