3 ms·
I'm a little confused by the pricing claims. They provide only one data point, a 24 CPU / 48 GB cluster. If your project can run in such a small amount of res
by metadat 4y ago
I'm a little confused by the pricing claims. They provide only one data point, a 24 CPU / 48 GB cluster. If your project can run in such a small amount of resources, is accumulating the complexity tax which comes with Kubernetes distributed system going to be a win? Would be significantly more helpful to show the price points at various compute scales.
I just looked up the cost of Oracle Kubernetes Engine on OCI (Oracle Cloud) and it's provided for free, you only pay for the compute resources you use.
On AWS you pay something like $0.10/hr/node.
Also, where do these machines run? What regions are available? What IAM controls and security policies are available? What is the disaster recovery story? For most real businesses, controlling and guaranteeing these aspects and risk factors quickly become critical. Far more important than saving a couple of hundred bucks or even a grand a month.
I understand.. it's sad to realize these things, because a better Heroku PaaS is highly appealing to the developer in me.
Perhaps there's a market segment I'm unfamiliar with which is craving this product layout. I wish you all the best.
- Havoc 4y agoThere is a pricing page in the menu
- quickthrower2 4y agoDepends how managed it is. I feel like a cloud managed kubernetes can be simple enough to run, if you already have the experience. I dare say on par with the complexity of running a VM yourself.
- styren 4y agoWe used that particular comparison of 24 cpus/48GB partly because it was a benchmark used by another competitor and partly because we felt it was in line with expected usage for a small/medium size business. We're hosting with Hetzner and we have our one and only region in Germany right now, we'll be opening more regions during 2023. Access is granted to users on a per-cluster basis (we're planning to launch finer grained permissions), with clusters having RBAC. Perhaps you're right in that most developers are looking for a better Heroku, and looking at our current users many of them have infra or devops background. I've used k8s in most of my recent (small & big) projects due to the fact that it's got such a large ecoystem of tools and packages I can readily deploy to it. It's perhaps not the same use-case as most of the users of Heroku or Render, but that's not necessarily the type of use-case that we're hoping to solve.