3 ms·
If you are indie avoid it until you have 100 users and some revenue. The last thing you want is to be fiddling with k8s when you have 3 whole users and $0 reve
by borplk 8y ago
If you are indie avoid it until you have 100 users and some revenue.
The last thing you want is to be fiddling with k8s when you have 3 whole users and $0 revenue.
Unless your niche strongly requires fancy architecture start with a $5 VPS and take it up from there.
You will never look back and think "shit if only I had used k8s on day one it wouldn't have failed".
More often it's closer to "shit if I had focused on non-tech stuff more maybe it would have gone somewhere ... instead I spent 2 months fiddling with YAML files".
- Arqu 8y agoI strongly disagree. Initially, I've been reluctant to do so myself, however, once I read a bit more of it, it's actually fairly simple for simple things and just a bit more complex for very complex stuff. It's no harder or more involved than setting up a VM on your own. The cost is also pretty much the same for small scale as you basically have free k8s masters by now. Also if you host a bunch of side projects, it's actually better in terms of resource utilization and separation of projects, it dynamically schedules pods based on resource requests across the nodes it has at hand so you can host several projects fully separate on a single or a handful of nodes depending on requirements.