fastify-ata
v0.6.0
Published
Fastify plugin for ata-validator. Runtime-competitive with the default, 24x faster serverless cold start, Standard Schema V1.
Maintainers
Readme
fastify-ata
Fastify plugin for ata-validator - JSON Schema validation powered by simdjson.
Drop-in replacement for Fastify's default ajv validator. Standard Schema V1 compatible.
Install
npm install fastify-ataUsage
const fastify = require('fastify')()
const fastifyAta = require('fastify-ata')
fastify.register(fastifyAta)
fastify.post('/user', {
schema: {
body: {
type: 'object',
properties: {
name: { type: 'string', minLength: 1 },
age: { type: 'integer', minimum: 0 },
role: { type: 'string', default: 'user' }
},
required: ['name']
}
}
}, (req, reply) => {
// req.body.role === 'user' (default applied)
reply.send({ ok: true, name: req.body.name })
})
fastify.listen({ port: 3000 })All your existing JSON Schema route definitions work as-is.
TypeScript
Write plain JSON Schema and get typed route handlers, no builder DSL. Add the AtaTypeProvider and author schemas with defineSchema:
import Fastify from 'fastify'
import fastifyAta from 'fastify-ata'
import { defineSchema } from 'ata-validator'
const app = Fastify().withTypeProvider<fastifyAta.AtaTypeProvider>()
await app.register(fastifyAta)
app.post('/user', {
schema: {
body: defineSchema({
type: 'object',
properties: { name: { type: 'string' }, age: { type: 'integer' } },
required: ['name'],
}),
},
}, (req, reply) => {
req.body.name // string
req.body.age // number | undefined
reply.send({ ok: true })
})defineSchema preserves the schema's literal types, so request.body, request.query, request.params, and request.headers are inferred from the schema. Same idea as @fastify/type-provider-typebox, from plain JSON Schema.
ata-validator falls back to a pure-JS engine where the native addon is not available (Cloudflare Workers, browsers, Bun), so fastify-ata runs in those environments too.
Chainable authoring (TypeBox-style)
If you prefer a chainable builder over JSON Schema literals, ata-validator/t emits the same plain JSON Schema under the hood, so route schemas, the type provider, and the AOT path all keep working without an adapter. The migration from TypeBox is one import rename:
import Fastify from 'fastify'
import fastifyAta from 'fastify-ata'
import { t } from 'ata-validator/t'
const app = Fastify().withTypeProvider<fastifyAta.AtaTypeProvider>()
await app.register(fastifyAta)
const Body = t.object({
name: t.string({ minLength: 1 }),
age: t.integer({ minimum: 0 }),
email: t.optional(t.string({ format: 'email' })),
role: t.union([t.literal('admin'), t.literal('user')]),
})
app.post('/users', { schema: { body: Body } }, (req, reply) => {
req.body.name // string
req.body.email // string | undefined
req.body.role // 'admin' | 'user'
reply.send({ ok: true })
})Options
fastify.register(fastifyAta, {
coerceTypes: true, // convert "42" -> 42 for integer fields
removeAdditional: true, // strip properties not in schema
abortEarly: true, // skip detailed error collection (faster invalid path)
prettyErrors: true, // 400 message carries the ATA code + a did-you-mean
})With prettyErrors, a failed request returns a compiler-style message instead of the plain ajv text:
body must have required property 'name' [ATA7001] (did you mean `name` instead of `nme`?)Off by default to keep the ajv-compatible message shape.
abortEarly replaces the error list with a shared stub. Good for public endpoints where only the accept/reject decision reaches the caller. On a 10-property schema the invalid path drops from roughly 15 ns/op to 3.7 ns/op.
Standalone Mode (Pre-compiled)
Drop-in replacement for @fastify/ajv-compiler/standalone. Same API.
const StandaloneValidator = require('fastify-ata/standalone')
// Build phase (once) - compile schemas to JS files
const app = fastify({
schemaController: { compilersFactory: {
buildValidator: StandaloneValidator({
readMode: false,
storeFunction(routeOpts, code) {
fs.writeFileSync(generateFileName(routeOpts), code)
}
})
}}
})
// Read phase (every startup) - load pre-compiled, near-zero compile time
const app = fastify({
schemaController: { compilersFactory: {
buildValidator: StandaloneValidator({
readMode: true,
restoreFunction(routeOpts) {
return require(generateFileName(routeOpts))
}
})
}}
})Standard Schema V1
ata-validator natively implements Standard Schema V1 - the emerging standard for TypeScript-first schema libraries.
const { Validator } = require('ata-validator')
const v = new Validator(schema)
// Standard Schema V1 interface
const result = v['~standard'].validate(data)
// { value: data } on success
// { issues: [{ message, path }] } on failureWorks with Fastify v5's Standard Schema support, tRPC, TanStack Form, Drizzle ORM.
What it does
- Registers a custom
validatorCompilerusing ata-validator - Applies
defaultvalues,coerceTypes,removeAdditionalduring validation - Caches compiled schemas (WeakMap) for reuse across routes
- Returns Fastify-compatible validation errors on invalid requests (400)
- Works with Fastify v4 and v5
Performance
All numbers below are reproducible on M4 Pro / Node 25 with the benchmarks in this repo and in ata-validator/benchmark. Run-to-run noise is roughly +/- 5% at these scales.
Fastify pipeline (autocannon, 10 connections, pipelining 10)
| Payload | ajv (default) | ata | delta | |---|---|---|---| | valid (10 fields) | ~70,000 req/s | ~70,500 req/s | tied | | invalid (10 fields) | ~51,000 req/s | ~52,500 req/s | +3% | | invalid (abortEarly) | ~51,000 req/s | ~52,800 req/s | +3.5% |
HTTP + JSON.parse + routing dominate the pipeline, so validator choice is small on throughput. The real difference is elsewhere.
Where ata-validator moves the needle
| Scenario | ajv | ata | delta |
|---|---|---|---|
| Serverless cold start (10 routes, first request) | 12.4 ms | 0.5 ms | 24x faster |
| Startup (200 routes) | 7.0 ms | 2.4 ms | 2.9x faster |
| Invalid validation (with abortEarly) | ~15 ns/op | 3.7 ns/op | 4x faster |
| ReDoS pattern ^(a+)+$ | 765 ms | 0.3 ms | immune (RE2) |
Serverless cold start is the scenario that matters for Vercel, Cloudflare Workers, Fly.io and similar platforms. On a long-running box the gap closes, so classic servers will not see a throughput jump.
Build-time compile (optional)
For browser / edge deployments, ata ships an ata compile CLI that turns a JSON Schema into a self-contained .mjs plus TypeScript declarations.
npx ata compile schemas/user.json -o src/user.validator.mjs --name UserA 10-field schema produces:
| Variant | Raw | Gzipped |
|---|---|---|
| ata runtime bundle | 117 KB | 27 KB |
| ata compile standard | 4.9 KB | 1.2 KB |
| ata compile --abort-early | 1.3 KB | 0.6 KB |
Generated file has zero runtime dependency on ata-validator. isValid is emitted as a TypeScript type predicate, so consumers get narrowing out of the box.
Features worth calling out
- RE2 regex - linear-time guaranteed, immune to catastrophic backtracking
- simdjson - SIMD-accelerated JSON parsing for buffer-input paths
- Multi-core -
countValid(ndjsonBuf)validates many messages in one native call - Standard Schema V1 - native support, works with Fastify v5, tRPC, TanStack Form, Drizzle
- Draft 2020-12 and Draft 7 - 98.5% compliance on the official JSON Schema Test Suite
License
MIT
