The architecture behind a one-person tech startup

Click for: original source

This is a long-form post breaking down the setup author uses to run a SaaS. From load balancing to cron job monitoring to payments and subscriptions. There’s a lot of ground to cover, so buckle up! By Anthony N. Simon.

In this article author talks about a low-stress, one-person company that he runs from his flat in Germany. It’s fully self-funded, and author likes to take things slow. It’s probably not what most people imagine when somebody says “tech startup”.

A high-level overview of the architecture


The article content:

  • A bird’s eye view
  • Automatic DNS, SSL, and Load Balancing
  • Automated rollouts and rollbacks
  • Let it crash
  • Horizontal autoscaling
  • Static assets cached by CDN
  • Application data caching
  • Per endpoint rate-limiting
  • Running scheduled jobs
  • Keeping secrets
  • Kubernetes manifests for app deployments

…and much more. You will get plenty of charts and links to services author uses. Nice one!

[Read More]

Tags startups app-development web-development kubernetes