Infrastructure
Infrastructure: enough to run well, not enough to drown in.
The architecture feels too complex, or Kubernetes is on the table before there is a problem to solve. Infrastructure should follow demand. This is where I help founders right-size it.
- The architecture feels overly complex.
- Do I need Kubernetes?
- Dedicated servers or cloud?
- Managed or in-house?
Start here
Targeted starting points for this area.
Frameworks for this area
Do I Need Kubernetes?
An honest decision framework for founders considering Kubernetes. Most startups do not need it, here is when they do, what to choose instead, and the questions to answer first.
Dedicated servers or cloud?
Dedicated servers give the best price-per-performance and predictable bills; cloud gives elasticity and managed services at a premium. A decision framework for founders choosing between bare-metal and public cloud.
Monolith or microservices?
Most startups choose microservices years before they need them. A decision framework for founders weighing the cost of complex architecture against the speed of a monolith.
What hosting do I need?
Most startups overestimate their infrastructure requirements. A decision framework for founders choosing between shared hosting, VPS, dedicated, cloud and Kubernetes.
Will Kubernetes actually solve your problem?
Sometimes yes. More often than not, no. Kubernetes is a tool, not a goal.