Server Batch

The batch handler processes multiple procedure calls in one HTTP round-trip. It pairs with the client-side BatchLink to reduce network overhead when your UI makes many calls at once.

Setup

import { createBatchHandler } from 'silgi/plugins'

const batchHandler = createBatchHandler(appRouter, {
  context: (req) => ({ db: getDB() }),
  maxBatchSize: 20,
})

Mount alongside your normal handler — for example at /batch:

// Using handler()
const handle = s.handler(appRouter)

export default {
  async fetch(request: Request) {
    const url = new URL(request.url)
    if (url.pathname === '/batch') return batchHandler(request)
    return handle(request)
  },
}

Protocol

The client sends a POST with a JSON array of calls:

[
  { "path": "users/list", "input": { "limit": 10 } },
  { "path": "users/get", "input": { "id": 1 } }
]

The server returns a JSON array of results (same order):

[{ "data": [{ "id": 1, "name": "Alice" }] }, { "data": { "id": 1, "name": "Alice", "email": "[email protected]" } }]

If a call fails, its entry has an error instead of data:

[
  { "data": [{ "id": 1, "name": "Alice" }] },
  { "error": { "code": "NOT_FOUND", "status": 404, "message": "User not found" } }
]

Options

All calls in a batch share the same context (computed once from the HTTP request). Each call runs the full compiled pipeline including guards, wraps, and validation.

Client setup

Use BatchLink from the client plugins:

import { BatchLink } from 'silgi/client/plugins'

const link = new BatchLink({
  url: 'http://localhost:3000',
  batchEndpoint: '/batch',
  maxBatchSize: 10,
})

What's next?

• Client plugins — BatchLink configuration
• Plugins — other available plugins