// Articles
Guides, tutorials, and comparisons to help you build better backend applications.
Let clients upload files straight to S3 from a Go API with presigned PUT URLs, using the AWS SDK for Go v2 with your own bucket, IAM and CORS, or Encore's signed upload URLs on a bucket declared in code.
When to use Cloud Tasks for explicit, rate-limited calls to one endpoint and when to use Pub/Sub for events with several consumers, with the limits that decide it, and how Encore provisions Pub/Sub on GCP from code.
How SNS topics and EventBridge event buses differ on routing, fan-out, latency, ordering and pricing, which one fits service-to-service events, and how Encore gives you SNS and SQS from a topic declared in code.
How the two AWS services differ on rotation, pricing, size limits and throughput, which one fits API keys, database passwords and plain config, and how Encore handles application secrets in your own AWS account.
Map each Heroku Scheduler job to a scheduled task in your own AWS account, either as an Encore cron job next to the code or as EventBridge Scheduler running an ECS task.
Move a Render Postgres database into Amazon RDS in your own AWS account with pg_dump and pg_restore, a short write freeze and a checked cutover, then point the app at it from Encore or a hand-built RDS setup.
Connect an Echo API in Go to PostgreSQL with migrations and a local database, using Encore or pgx with Amazon RDS.
Schedule recurring work for a Gin API in Go, from robfig/cron inside the process to Encore cron jobs that keep running when the app scales to several instances.
Publish events from Gin handlers and process them in a subscriber with retries, a dead-letter queue and idempotent handling, using Encore or SNS and SQS wired by hand.
A decision by team and project type: when Terraform or OpenTofu earns its place, when it is overhead, and what to use instead.
Six guardrails for letting agents ship backend changes to your own AWS or GCP, how to apply each one with any tooling, and which platforms enforce them.
Terragrunt explained: what it adds on top of OpenTofu and Terraform, how units, includes, dependencies and stacks work, what changed in 1.0 and when it is worth adopting.