Live data from Hacker News

Hakuna Cloud – Stop cloud servers when they are not in use

hakuna.cloud

1–10 of 64 posts

Re: Hakuna Cloud – Stop cloud servers when they are not in use

#3
Efficiency is an area where there can be a lot of cost hiding. We recently saved a lot of money by:

- Using the Kubernetes Vertical Pod Autoscaler (https://github.com/kubernetes/autoscaler/tree/master/vertica...) for CPU and memory scaling, and switching to metrics like requests per second and connection count for horizontal scaling

- Collecting metrics on container CPU and memory allocation vs utilization

- Writing scripts to auto-submit PRs to SREs with better recommended sizing based on actual usage

- Tuning our VM instance sizes and autoscaler configs

A few engineers were able to save the company several times their salary with a few months of work, and plan to 10x the savings over the next year

Re: Hakuna Cloud – Stop cloud servers when they are not in use

#4
post #3

Efficiency is an area where there can be a lot of cost hiding. We recently saved a lot of money by: - Using the Kubernetes Vertical Pod Autoscaler ( https://github.com/kubernetes/autoscaler/tree/master/vertica... ) for CPU and memory scaling, and switching to metrics like requests per second and connection count for horizontal scaling - Collecting metrics on container CPU and memory allocation vs utilization - Writin…

Actually, HakunaCloud works on cloud servers, not containers. With Kubernetes you pay for the worker nodes, not for running containers.

HakuaCloud starto&stop cloud servers, so you actually pay only for the time the servers are needed

Re: Hakuna Cloud – Stop cloud servers when they are not in use

#7
post #5

Interesting idea. Almost bring the idea of lambda to VMs, doesn't it? Also, how does hakuna work with DO? I thought DO still charges when VMs are powered off?

Hi, I'm a developer at Hakuna. Thank you for the feedback.

With DO, we destroy the instance so that nothing is charged for it, and save a snapshot to be used to restart the instance; you pay only for the snapshot storage - $0.05/GB per month.

Re: Hakuna Cloud – Stop cloud servers when they are not in use

#8
> Hakuna Cloud is a software-as-a-service HTTPS proxy. You don't need to change existing software or infrastructure, and you don't need to install additional tools on your servers.

> Each cloud server must have an FQDN/DNS name configured as a CNAME to our load balancers.

> When your server stops receiving requests, it will be stopped. As soon as a new request arrives, Hakuna will start it.

Interesting idea. It's like a proxy that kind of makes an instance/vm-based service act like a serverless service, without moving to containers or rewriting.

Seems kind of niche but I can see the use: there's a lot of services that have a time-based usage pattern (during working hours, or used interactively for a few minutes/hours sparsely through the day).

What are the cold start times like with this (at least for a typical, simple app - say on asp.net on Windows or something hosted via nginx on Linux)? What happens if an instance is being stopped and a new request comes in - does the request have to wait for shutdown plus startup?

Re: Hakuna Cloud – Stop cloud servers when they are not in use

#9
post #3

Efficiency is an area where there can be a lot of cost hiding. We recently saved a lot of money by: - Using the Kubernetes Vertical Pod Autoscaler ( https://github.com/kubernetes/autoscaler/tree/master/vertica... ) for CPU and memory scaling, and switching to metrics like requests per second and connection count for horizontal scaling - Collecting metrics on container CPU and memory allocation vs utilization - Writin…

Very nice! I suspect the economy of Cloud will soon change in such a way that Cloud providers will be focusing more on Enterprise, which have very little capability of doing similar things. And then, a lot of companies like Hakuna Cloud (reported here) will emerge, just like what happened in the last iteration of IT infrastructure.
Post reply on HN