import Queue from "encore/queue"; export const emailQueue = new Queue("emails", maxConcurrency: 10, );
When you deploy, Encore.ts parses this, creates the necessary cloud resources (RDS, Cloud SQL, etc.), and runs your migrations automatically. Forget generating OpenAPI specs (Swagger) and praying your frontend matches. With Encore.ts, your backend endpoints define request/response shapes, and Encore automatically generates a fully type-safe TypeScript client: encore ts
import ping from "./client"; // auto-generated const result = await ping( name: "World" ); // fully typed Encore.ts treats background jobs as first-class citizens. You define a queue, and Encore handles the message broker (e.g., Redis, SQS, GCP Pub/Sub): import Queue from "encore/queue"; export const emailQueue =
is a new breed of TypeScript backend framework that flips the script. It is not just an HTTP router; it is a complete backend development platform that includes infrastructure tooling, type-safe clients, and built-in distributed systems primitives. What is Encore.ts? Developed by the team behind Encore (originally a Go framework), Encore.ts brings the same "backend development platform" philosophy to TypeScript. It is an opinionated framework that compiles your TypeScript code into a deployable backend, automatically handling infrastructure provisioning (like databases, queues, and cron jobs) and generating idiomatic API clients. You define a queue, and Encore handles the message broker (e
It is still young (first stable release in late 2024), but for greenfield projects, it represents a genuine leap forward in TypeScript backend ergonomics.
For years, building a backend in TypeScript has followed a predictable pattern: grab express or Fastify , add some zod for validation, wire up a few ts-node scripts, and pray your async error handling doesn't silently fail. While this works, it feels bolted together.