// Articles
Guides, tutorials, and comparisons to help you build better backend applications.
Five ways to get a Heroku-style workflow inside your own AWS account, compared on what you pay besides the AWS bill and what you still have to build.
Build the backend that records seller earnings, holds funds through the refund window, batches daily payouts and sends Stripe Connect transfers exactly once, with the hand-built AWS path and the same design in Go with Encore.
Build the backend for first notice of loss, claim documents, automated triage, adjuster SLAs and an audit trail of every status change, with the hand-built AWS path and the same design in TypeScript with Encore.
Build the backend that receives device readings from gateways or AWS IoT Core, buffers them, stores them in Postgres, keeps the latest state per device and rolls up history, with the hand-built AWS path and the same design in Go with Encore.
Schema migration tools that replace Liquibase changelogs, from Encore's migrations applied on run and deploy to Flyway, Atlas, golang-migrate, Sqitch and dbmate, with what each one does differently.
The main tools for moving workloads to AWS and Google Cloud, grouped by what they move, with what each one leaves for you to do, and where an infrastructure SDK fits when the application is re-platformed rather than copied.
How OpenTelemetry instrumentation works for backend services, when zero-code agents are enough and when you need manual spans, what it takes to run in production, and how Encore traces services without instrumentation code.
How each Kubernetes deployment strategy works, the YAML behind it, what it needs beyond a Deployment, and how Encore rolls out services on EKS or Fargate in your own AWS account without the manifests.
Three ways to turn a push to GitHub into a running backend in your own cloud account: Encore's GitHub integration, GitHub Actions with OIDC, and AWS CodePipeline, with what each one leaves you to set up.
Concrete Terraform for an ElastiCache replication group with a subnet group, security group, parameter group, encryption and failover, what keeps costing time after the first apply, and how Encore provisions caches from code.
Concrete Terraform for a private S3 bucket using the split resources of AWS provider v4 and later, the IAM and naming problems that follow, and how Encore provisions buckets from code instead.
Concrete Terraform for an SQS queue with a redrive policy, an SNS subscription and the IAM a producer and consumer need, the settings that bite later, and how Encore provisions the same queues from code.