Earlier quoted context omitted.
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 service…
https://www.cloudhealthtech.com/
Hakuna Cloud – Stop cloud servers when they are not in use
51–60 of 64 posts
Re: Hakuna Cloud – Stop cloud servers when they are not in use
#52Efficiency 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…
Do you run kubernetes in VMs on baremetal?
Re: Hakuna Cloud – Stop cloud servers when they are not in use
#53Efficiency 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…
Re: Hakuna Cloud – Stop cloud servers when they are not in use
#54Interesting. Why proxying though rather than monitoring DNS queries on the CNAME? And updating to point to the right ip when the server is live (This could maybe help with the 10gb base limit + $0.08/gb?) Not trying to be an armchair coach but rather understand the architecture decisions and trade-offs that I must have missed
Re: Hakuna Cloud – Stop cloud servers when they are not in use
#55That's the next generation of Lambda that all clouds and vendors are moving towards, and increases developer agility with much faster cold-start times. If we could have Cloud Run today across multiple clouds and locations with geo-loadbalancing stitched together automatically, that would be valuable.
Re: Hakuna Cloud – Stop cloud servers when they are not in use
#56It'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 service…
Re: Hakuna Cloud – Stop cloud servers when they are not in use
#57Re: Hakuna Cloud – Stop cloud servers when they are not in use
#58Efficiency 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…
Re: Hakuna Cloud – Stop cloud servers when they are not in use
#59> 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 lik…
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…
Re: Hakuna Cloud – Stop cloud servers when they are not in use
#60Interesting. Why proxying though rather than monitoring DNS queries on the CNAME? And updating to point to the right ip when the server is live (This could maybe help with the 10gb base limit + $0.08/gb?) Not trying to be an armchair coach but rather understand the architecture decisions and trade-offs that I must have missed
What happens where there are no servers live? Should the request fail?