Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

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

hakuna.cloud

Post reply on HN
Print view View original

21–30 of 64 posts

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

#21

Post by tarl0s »

gregmac wrote: post #19
tarl0s wrote: post #13

Earlier quoted context omitted.

At Hakuna we use our own service to start and stop our Jira and NPM servers; the instances are automatically stopped at night or whenever nobody needs to do `npm install`. In our use case, the EC2 instance starts in about 50 seconds, with another minute needed to start the Jira service. We have a demo, deployable directly from our CLI, that starts a Nginx server on an Oracle Cloud instance in less than 40 seconds. If…

Thanks. Is there UI feedback to the user during the wait, or does the browser just show "waiting for response" for the whole time? If a user refreshes the browser a bunch of times during the wait, will the Hakuna proxy give up on those requests or still pass all of them through to the target server?

We cannot provide UI feedback during the wait: being a HTTPS proxy, we would need the SSL certificate to reply to the request, otherwise it would be some kind of MitM.

If the client closes the socket before the start of the server, the proxy gives up on its requests.

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

#22

Post by colechristensen »

najarvg wrote: post #11
dharmab wrote: 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…

Would love to see a more detailed write-up, if one exists, on your experience. We're nowhere near your scale but will probably ramp up in the next year or so.

During a ramp up the limiting factor is usually engineer hours, new features, and ability to have the load at all and not cost.

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

#25

Post by p-schultz »

tarl0s wrote: post #18
ssttevee wrote: post #17

From the FAQ: > The HTTPS trigger is intercepting all my traffic? > No, your data are safe if your server support HTTPS protocol. All the data exchanged between your server and your clients is encrypted and not accessible by us. Unless there's an IP allocated to each user, I don't think this is accurate. With SSL, the HTTP headers are encrypted, so there would be no way to know where know where to route the request w…

In HTTPS, all the headers are encrypted except the hostname: https://en.wikipedia.org/wiki/Server_Name_Indication SSL termination is always done on our customers' servers.

The whole header is encrypted, including the Host header and request line. Certificate selection and routing relies on SNI[1]. The server name in the TLS client hello message is almost always, but not necessarily, a copy of the value of the Host header field.

[1]: https://en.m.wikipedia.org/wiki/Server_Name_Indication

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

#26

Post by entscheidungsP »

comeonman1 wrote: post #20
alanbernstein wrote: post #10

I just had a conversation about this product idea a couple days ago. How long before Amazon acquires it and cripples the functionality? Could be a good exit strategy, at least.

2 minute cold start is pretty slow for a lot of use cases... Amazon already built Lambda which is more widely applicable.

True, I think lambda would be a better choice for new projects. However, for old monolith projects, this sounds like a great way to cut costs on dev/staging servers.

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

#27

Post by wheelerwj »

> You don't need to change existing software or infrastructure, and you don't need to install additional tools on your servers.

then

> Install Hakuna CLI

and

> Update the DNS

That certainly sounds like installing things and making changes to your infrastructure...

It sounds like a cool idea for sure and can be really helpful for a lot of companies but this seems like an outright lie.

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

#28

Post by grepthisab »

tlarkworthy wrote: post #12

It's pretty cool that utility computing is large enough to spawn 3rd party companies that further increase effeciency of the pool. It's layers upon layers of technical progress in parallel.

Maybe. This is a bit of a cottage industry that shouldn't need to exist. It's so hard to get data and visibility into these things in AWS right now. Billing is hard, it's impossible to easily tell what is costing me what in every region, etc. AWS should do all this natively as part of their service, but everything is so poorly designed from a user standpoint that it's very time consuming to do, so third-party services like Hakuna pop up to take advantage of the inefficiency by saving some money. I'm halfway convinced AWS does this on purpose so you have to pay them for support or training for people new to cloud service providers, or AWS specifically, increasing their revenue.

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

#29

Post by SparkyMcUnicorn »

wheelerwj wrote: post #27

> You don't need to change existing software or infrastructure, and you don't need to install additional tools on your servers. then > Install Hakuna CLI and > Update the DNS That certainly sounds like installing things and making changes to your infrastructure... It sounds like a cool idea for sure and can be really helpful for a lot of companies but this seems like an outright lie.

Installing the CLI is optional.

"npm install @hakuna.cloud/cli -g and you are ready to go. Or use the web dashboard!"

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

#30

Post by tarl0s »

wheelerwj wrote: post #27

> You don't need to change existing software or infrastructure, and you don't need to install additional tools on your servers. then > Install Hakuna CLI and > Update the DNS That certainly sounds like installing things and making changes to your infrastructure... It sounds like a cool idea for sure and can be really helpful for a lot of companies but this seems like an outright lie.

Hi, I work at Hakuna Cloud as a developer. Thanks for your feedback.

If you don't like the idea of updating your DNS records, Hakuna provides a hostname creation feature for trying the product (*.demo.hakuna.cloud CNAME records that point to our load balancers).

You can install the Hakuna CLI on your laptop, no need to have it on the cloud instances. Also, most of the features you can find on the CLI are also available on the web dashboard.

Post reply on HN