Named entrypoints

content/workers/runtime-apis/bindings/service-bindings/rpc.md

@@ -102,7 +102,90 @@ export default class extends WorkerEntrypoint {
 
 ## Named entrypoints
 
-TODO: Example
+You can also export any number of named `WorkerEntrypoint` classes from within a single Worker, in addition to the default export. You can then declare a Service binding to a specific named entrypoint.
+
+You can use this to group multiple pieces of compute together. For example, you might create a distinct `WorkerEntrypoint` for each permission role in your application, and use these to provide role-specific RPC methods:
+
+```toml
+---
+filename: wrangler.toml
+---
+name = "todo-app"
+
+[[d1_databases]]
+binding = "D1"
+database_name = "todo-app-db"
+database_id = "<unique-ID-for-your-database>"
+```
+
+```js
+import { WorkerEntrypoint } from "cloudflare:workers";
+
+export class AdminEntrypoint extends WorkerEntrypoint {
+  async createUser(username) {
+    await this.env.D1.prepare("INSERT INTO users (username) VALUES (?)")
+      .bind(username)
+      .run();
+  }
+
+  async deleteUser(username) {
+    await this.env.D1.prepare("DELETE FROM users WHERE username = ?")
+      .bind(username)
+      .run();
+  }
+}
+
+export class UserEntrypoint extends WorkerEntrypoint {
+  async getTasks(userId) {
+    return await this.env.D1.prepare(
+      "SELECT title FROM tasks WHERE user_id = ?"
+    )
+      .bind(userId)
+      .all();
+  }
+
+  async createTask(userId, title) {
+    await this.env.D1.prepare(
+      "INSERT INTO tasks (user_id, title) VALUES (?, ?)"
+    )
+      .bind(userId, title)
+      .run();
+  }
+}
+
+export default class extends WorkerEntrypoint {
+  async fetch(request, env) {
+    return new Response("Hello from my to do app");
+  }
+}
+```
+
+You can bind to `AdminEntrypoint` and `UserEntrypoint` with a Service binding:
+
+```toml
+---
+filename: wrangler.toml
+---
+name = "admin-app"
+
+[[services]]
+binding = "ADMIN"
+service = "todo-app"
+entrypoint = "AdminEntrypoint"
+```
+
+```js
+export default {
+  async fetch(request, env) {
+    await env.ADMIN.createUser("aNewUser");
+    return new Response("Hello from admin app");
+  },
+};
+```
+
+You can learn more about how to configure D1 [here](/d1/get-started/#4-bind-your-worker-to-your-d1-database)
+
+You can try out a complete example of this to do app, as well as a Discord bot built with named entrypoints, by cloning the [cloudflare/js-rpc-and-entrypoints-demo repository](https://github.com/cloudflare/js-rpc-and-entrypoints-demo) from Github.
 
 ## Further reading
 

content/workers/wrangler/configuration.md

@@ -713,7 +713,7 @@ To bind Queues to your producer Worker, assign an array of the below object to t
 - `binding` {{<type>}}string{{</type>}} {{<prop-meta>}}required{{</prop-meta>}}
 
   - The binding name used to refer to the queue in your Worker. The binding must be [a valid JavaScript variable name](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Guide/Grammar_and_types#variables). For example, `binding = "MY_QUEUE"` or `binding = "productionQueue"` would both be valid names for the binding.
- 
+
 - `delivery_delay` {{<type>}}number{{</type>}} {{<prop-meta>}}optional{{</prop-meta>}}
 
   - The number of seconds to [delay messages sent to a queue](/queues/reference/batching-retries/#delay-messages) for by default. This can be overridden on a per-message or per-batch basis.
@@ -762,7 +762,7 @@ To bind Queues to your consumer Worker, assign an array of the below object to t
 
   - The maximum number of concurrent consumers allowed to run at once. Leaving this unset will mean that the number of invocations will scale to the [currently supported maximum](/queues/platform/limits/).
   - Refer to [Consumer concurrency](/queues/reference/consumer-concurrency/) for more information on how consumers autoscale, particularly when messages are retried.
- 
+
 - `retry_delay` {{<type>}}number{{</type>}} {{<prop-meta>}}optional{{</prop-meta>}}
 
   - The number of seconds to [delay retried messages](/queues/reference/batching-retries/#delay-messages) for by default, before they are re-delivered to the consumer. This can be overridden on a per-message or per-batch basis [when retrying messages](/queues/reference/batching-retries/#explicit-acknowledgement-and-retries).
@@ -889,6 +889,10 @@ To bind other Workers to your Worker, assign an array of the below object to the
 
   - The name of the Worker.
 
+- `entrypoint` {{<type>}}string{{</type>}} {{<prop-meta>}}optional{{</prop-meta>}}
+
+  - The name of the [entrypoint](content/workers/runtime-apis/bindings/service-bindings/rpc/#named-entrypoints) to bind to. If you do not provide a value, the default export of the Worker will be used.
+
 {{</definitions>}}
 
 Example:
@@ -898,14 +902,15 @@ Example:
 header: wrangler.toml
 ---
 services = [
-  { binding = "<BINDING_NAME>", service = "<WORKER_NAME>" }
+  { binding = "<BINDING_NAME>", service = "<WORKER_NAME>", entrypoint = "<ENTRYPOINT_NAME>" }
 ]
 
 # or
 
 [[services]]
 binding = "<BINDING_NAME>"
 service = "<WORKER_NAME>"
+entrypoint = "<ENTRYPOINT_NAME>"
 ```
 
 ### Analytics Engine Datasets