Racket Web

Racket for Lisp-based web apps.

BackendComplex

Stack Components

LanguageRacket 8.14

Frameworkracket/web-server

DBracket/db

DBPostgreSQL 16

Why

Language-oriented, macros, continuations. Node.js, Go, and Python are the top 3 backend languages (Stack Overflow 2024).

Go's goroutines handle 100k+ concurrent connections per process; Node's event loop excels at I/O-bound workloads.

When

Use for DSL web apps. Avoid for performance-critical.

How

1. raco pkg install web-server 2. Define servlets 3. raco run app.rkt 5. Add environment configuration — cp .env.example .env && edit values 6. Run tests — npm test or pnpm test to verify setup 7. Deploy — git push to trigger CI/CD or manual deploy

Example

(define (start req) (response/xexpr `(html (body ,users)))) // Racket Web — usage example import { RacketWeb } from "racket-racket"; const result = await racketweb({ input: "data" }); console.log(result);

Common Problems

⚠Continuations — use send/suspend
⚠Templates — use xexpr
⚠Configuration drift between environments — use infrastructure-as-code (Terraform/Pulumi) to keep dev/staging/prod identical

Best Practices

✓Use Racket macros for DSLs
✓Leverage DrRacket for dev
✓Set up health checks and graceful shutdown — handle SIGTERM to drain in-flight requests before exit

FAQ

What is Racket Web and what projects is it for?

Racket for Lisp-based web apps. It pairs layered technologies for end-to-end type safety and out-of-the-box deploys, fitting everything from MVPs to production SaaS.

How do I spin up a working demo with Racket Web in 10 minutes?

Two steps: (1) raco pkg install web-server; (2) Define servlets. Get the local dev server running, then wire one real data source to verify the end-to-end loop.

What is the most common pitfall with Racket Web and how do I avoid it?

The most common pitfall is: Continuations — use send/suspend. Avoid it by adding the matching checklist to your PR template and running type-check + lint + unit tests in CI — three gates before merge.

What are the best practices for Racket Web?

Best practices for Racket Web include: Use Racket macros for DSLs; Leverage DrRacket for dev; Set up health checks and graceful shutdown — handle SIGTERM to drain in-flight requests before exit. The first one — "Use Racket macros for DSLs" — should be set up at project init to avoid costly rework later.

When should I NOT choose Racket Web?

Pick something else in three cases: (1) the team has zero experience with the core framework and the deadline is tight (learning-curve risk); (2) it's a pure content/marketing site (Astro is lighter); (3) you need very high throughput (>10k RPS) or strict-consistency microservices (Go/Rust). Racket Web shines for mid-to-high complexity full-stack and API work — don't over-engineer simple static pages with it.