This has been done forever. Ops team had cronjobs to restart misbehaving applications out of business hours since before I started working. In a previous job, the solution for disks being full on a VM on-prem (no, not databases) was an automatic reimage. I've seen scheduled index rebuilds on Oracle. The list goes on.
> I've seen scheduled index rebuilds on Oracle
If you do look into the Oracle dba handbook, scheduled index rebuilds are somewhat recommended. We do it on weekends on our Oracle instances. Otherwise you will encounter severe performance degredation in tables where data is inserted and deleted at high throughput thus leading to fragmented indexes. And since Oracle 12g with ONLINE REBUILD this is no problem anymore even at peak hours.
Rebooting Windows IIS instances every night has been a mainstay for most of my career. haha
I’ve got an IIS instance pushing eight years of uptime… auto pool recycling is disabled.
Amazon folks won’t debug your code though, they’ll just happily bill you more.
The point is not to spend time frantically fixing code at 3 AM.
This is not exactly a new tactic, and not something that would have to have been implemented without any cloud solution. A randomized 'kill -HUP' could do the same thing, for example.
Amazon needs wizards then.
You don’t need wizards in your team anymore.
Something seems off in the instance? Just nuke it and spin up a new one. Let the system debugging for the Amazon folks.