> Anecdotally, I’ve run several VPS servers over the years which all have well over 99.9% uptime and have suffered no catastrophic failures.
Without advocating for Kubernetes, there's a pretty big difference between running a single application like WordPress or whathaveyou that receives only occasional updates and a SaaS application that is actively developed by hundreds or thousands of engineers deploying dozens of times per day. Yes, Kubernetes is complex and that complexity can introduce its own downtime issues, but that risk is a large constant whereas without it the risk increases with the number of deployments (and deploying larger deltas less frequently carries its own penalties). It's important to understand and acknowledge these dynamics in order to optimize for uptime and velocity.
Yes, I agree there's definitely a place for Kubernetes. If you have thousands of engineers working on an application then workflow management becomes a very real concern. I've seen a lot of organizations adopt Kubernetes well before then though and I feel like it's a mistake. I didn't mean to imply that all Kubernetes applications should move to SQLite but that SQLite is a viable option for most small to medium sized applications with moderate uptime requirements.
Right, I didn't interpret you as trying to gloss over this nuance, but I've seen a lot of "always k8s vs never k8s" debates which suggests to me that people need the explicit disclaimer.
Without advocating for Kubernetes, there's a pretty big difference between running a single application like WordPress or whathaveyou that receives only occasional updates and a SaaS application that is actively developed by hundreds or thousands of engineers deploying dozens of times per day. Yes, Kubernetes is complex and that complexity can introduce its own downtime issues, but that risk is a large constant whereas without it the risk increases with the number of deployments (and deploying larger deltas less frequently carries its own penalties). It's important to understand and acknowledge these dynamics in order to optimize for uptime and velocity.