4 ms·

I am soon to venture in to SAAS business. Should I be interested in kubernetes ? Is old way of doing things still relevant?

brianwawok 8y ago
I would look hard at k8s or serverless. I went with k8s for my SaaS business and it is a huge competitive edge.
- Aduket 8y ago
  what do you mean by "competitive edge", do you regret choosing it? and why?
  - brianwawok 8y ago
    Competitive edge. Like it helps me beat my competition. My competitors deploy once a week. I deploy 30x a day. I get CI/CD for near free, which is amazing. All else equal between us, this will let me beat them to market. The opposite of regrets. I suggest k8s or serverless for almost anyone...
tnolet 8y ago
This completely depends on your business. Are you running many cloud based workloads in a Dockerized manner? Are you having trouble orchestrating, monitoring and scaling those workloads? Then use Kubernetes. In most if not all other cases, Heroku will probably get you through the first couple of years.
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 ago
  I 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.

brianwawok 8y ago

I would look hard at k8s or serverless. I went with k8s for my SaaS business and it is a huge competitive edge.

Aduket 8y ago
what do you mean by "competitive edge", do you regret choosing it? and why?
- brianwawok 8y ago
  Competitive edge. Like it helps me beat my competition. My competitors deploy once a week. I deploy 30x a day. I get CI/CD for near free, which is amazing. All else equal between us, this will let me beat them to market. The opposite of regrets. I suggest k8s or serverless for almost anyone...

tnolet 8y ago

This completely depends on your business. Are you running many cloud based workloads in a Dockerized manner? Are you having trouble orchestrating, monitoring and scaling those workloads? Then use Kubernetes. In most if not all other cases, Heroku will probably get you through the first couple of years.

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 ago
I 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.