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 the instance is being stopped and a new request arrives, it will have to wait shutdown + startup, yes.
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?
If the client closes the socket before the start of the server, the proxy gives up on its requests.
I'm looking forward to checking out Hakuna Cloud - looks like the two services are pretty complimentary.
> 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?