At the risk of sounding like an AWS apologist, this is really great if you have a use case for it. Don’t use it if you don’t. We’ve been waiting to use this fo

At the risk of sounding like an AWS apologist, this is really great if you have a use case for it. Don’t use it if you don’t. We’ve been waiting to use this for our dev and test environments - the devs and testers work irregular schedules, sometimes only a few hours a day and obviously 5 days a week. We currently have manual and semi automatic start and stop switches for those environments, can get rid of all that. Some of our systems are low volume high value - they kick into high gear once or twice a week (not necessarily on a schedule, whenever customers feel like placing and order) at which point hundreds of thousands of queries need to be run. We currently run large or extra large DB servers 24x7 at 0.01% overall utilisation because of this. Some of the services are used only during daytime at a single timezone, but once in a while there are a few night owls. It’s perfect for use cases like this. Sure, if you compare it cost wise to a similar 24x7 instance it’ll be more expensive. Sure, it takes lots of seconds at for a cold boot. Both these things are not the point. The tool is what it is, and it’s clear about its shortcomings in the same way that a Gatling gun is clear that it has a non negotiable spin up time. That doesn’t mean it’s not useful, it needs to be matched to the work it can do effectively.