Lua + Lapis

Lua + Lapis for lightweight APIs.

BackendModerate

Stack Components

LanguageLua 5.4

FrameworkLapis 1

ORMLapis ORM

DBPostgreSQL 16

Why

OpenResty-based, fast, embedded. 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 OpenResty apps. Avoid for non-Lua teams.

How

1. lapis new app 2. Define app routes 3. lapis server 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

app:match('/users', function(self) return { json = users } end) // Lua + Lapis — usage example import { LuaLapis } from "lua-lapis"; const result = await lualapis({ input: "data" }); console.log(result);

Common Problems

⚠OpenResty — use nginx for serving
⚠Coroutines — use ngx.timer.at for async
⚠Configuration drift between environments — use infrastructure-as-code (Terraform/Pulumi) to keep dev/staging/prod identical

Best Practices

✓Use Lapis migrations for DB
✓Leverage LuaJIT for speed
✓Set up health checks and graceful shutdown — handle SIGTERM to drain in-flight requests before exit

FAQ

What is Lua + Lapis and what projects is it for?

Lua + Lapis for lightweight APIs. 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 Lua + Lapis in 10 minutes?

Two steps: (1) lapis new app; (2) Define app routes. 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 Lua + Lapis and how do I avoid it?

The most common pitfall is: OpenResty — use nginx for serving. 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 Lua + Lapis?

Best practices for Lua + Lapis include: Use Lapis migrations for DB; Leverage LuaJIT for speed; Set up health checks and graceful shutdown — handle SIGTERM to drain in-flight requests before exit. The first one — "Use Lapis migrations for DB" — should be set up at project init to avoid costly rework later.

When should I NOT choose Lua + Lapis?

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). Lua + Lapis shines for mid-to-high complexity full-stack and API work — don't over-engineer simple static pages with it.