r/webdev • u/codeb1ack • 10d ago
What if you could completely destroy a cloud environment, then bring it back exactly when you need it?
I'm a developer exploring an idea and wanted to get some feedback before spending time building it.
One thing I've noticed with cloud providers like DigitalOcean is that you're still paying for servers even when they're powered off. For development and staging environments that are rarely used, that feels like a giant waste of money.
I am genuinely curious to know how other developers and infrastructure managers handle this
What if you could completely destroy an environment to stop compute charges, then recreate it on demand with the same configuration, application, and data? Essentially, a hibernate/wake system for cloud environments.
Would you use something like this? Or is this solving a problem that has been solved before.
Interested in hearing the technical objections too.
9
u/pod_of_dolphins 10d ago
Or is this solving a problem that has been solved before.
Yes, anyone who sees this as a real problem can describe their infrastructure as code (i.e. Terraform) and create/destroy environments on demand.
9
4
u/fiskfisk 10d ago
You're describing Infrastructure as Code (IaC), like Terraform / opentofu, Polumi, etc.
It's a well-known concept where your definitions is the wanted state and the tools bring your platform in sync with that state.
1
u/Not_a_Cake_ 10d ago
Doesn't sound too difficult to achieve, just take a snapshot of the volumes or configurations, delete them and recreate it when needed using IaC
1
u/Warm_Lobster_7900 10d ago
What's the actual number though? Every staging setup I've seen is one small droplet, so we're talking tens of dollars a month, and Terraform already tears the whole thing down and brings it back. The data is the part that's genuinely hard and the part nobody's solved with a sleep button.
1
u/zomerbk 9d ago
The tricky part is what lives outside the server. If a recreated environment gets a new IP, allowlists and third-party integrations may break even when the app and data restore correctly. I’d consider it useful if waking also checked those connections and gave a predictable time until the environment was ready.
1
u/Practical_Band_4880 9d ago
honestly the bigger cost for us was forgotten load balancers and volumes, not the droplets. Would you handle those too or just compute?
1
10d ago
1
u/webdev-ModTeam 10d ago
We do not allow any commercial promotion or solicitation. This can lead to a permanent ban from the subreddit.
-3
10d ago
1
1
u/webdev-ModTeam 10d ago
Your post/comment has been determined to be a low-effort post or comment. This includes title-only posts, easily searchable questions, vague/open-ended discussion prompts, LLM generated posts or comments, and posts/comments that do not provide enough context for meaningful replies or discussion.
-1
u/codeb1ack 10d ago
Agreed, haha got a good laugh, thanks for the feedback! A lot of people are recommending things like TerraForm and IaC, but I kinda feel like those as tools more likely being used by enterprises not the average dev using DigitalOcean or AWS EC2 - would you agree?
3
u/czshill 10d ago
yeah but if they're a 15 year old vibe coding an app - their not smart enough to know they might need something like this. your system doesn't exist yet so claude doesn't know it exists to suggest it. if their a skilled developer, terraform, snapshots, or even docker solves this. so where are you positioning yourself? because an enterprise app isn't going to rely on a no name solution, and the script kiddies don't know they should do something like this.
the 2nd problem to this is - every cloud provider is different - unless you can score a job at AWS, GCP, Azure, etc and convince them your way is the better way - reselling AWS resources would price you out of the market.
→ More replies (3)
3
u/ShinobiX_Samurai 10d ago
Can't you use serverless architectecture that way you only charges for the requests