// Articles
Guides, tutorials, and comparisons to help you build better backend applications.
Six TypeScript backend frameworks for teams that want less NestJS boilerplate, ranked, with versions, code and what each one asks you to give up.
What changes when cloud resources are declared in the application instead of in a separate Terraform, Pulumi or CDK codebase, with the same queue and bucket written both ways.
Design the dispatch backend for last-mile delivery: driver location pings in Redis, nearest-driver offers that expire, transactional assignment so no driver or parcel is double booked, and a sweep that redispatches, built by hand on AWS or in Go with Encore.
Design the backend behind assignment submissions: direct uploads to private storage, deadline and size checks, resubmissions, background fingerprinting to flag identical files and short-lived links for teachers, built by hand on AWS or in TypeScript with Encore.
Design the backend that sends 24-hour and 2-hour appointment reminders exactly when they are due, never twice, in the clinic's time zone and without medical details in the message, built by hand on AWS or in TypeScript with Encore.
Design the backend behind fintech customer onboarding: collect identity documents through signed uploads, start one verification check per application, accept signed provider webhooks and keep an auditable status trail, built by hand on AWS or in Go with Encore.
Terraform for a private Cloud Storage bucket with versioning, soft delete, lifecycle rules and CORS, IAM that lets a service create but not delete objects, and the permission signed URLs need on Cloud Run, plus how Encore provisions buckets from code.
A complete Terraform setup for an API on Amazon ECS Fargate behind an Application Load Balancer, with security groups, logs, deployment rollback and CPU autoscaling, the settings that cause failed deployments, and how Encore deploys to Fargate from code.
Terraform for Secrets Manager secrets whose values never reach state, a customer managed KMS key, read access for an ECS service, rotation options, and the deletion behavior that breaks re-applies, plus how Encore handles secrets from code.
Terraform for a Pub/Sub topic and pull subscription with retry and dead-letter policies, the IAM bindings that dead lettering quietly depends on, and how Encore provisions the same topics from Go or TypeScript.
Terraform for a Cloud SQL for PostgreSQL instance with private IP, backups and point-in-time recovery, a database user whose password never lands in state, and the settings that cause trouble later, plus how Encore provisions Cloud SQL from code.
Which IAM role on an Amazon ECS task definition does what, which permissions belong on each, the errors you get when they are swapped, and Terraform that sets both up for a Fargate service.