Idk how an AWS region would respond to a power outage, but i have tested this in AWS Outpost, and there, if you power down a rack, then power it back again, the baremetal instances will not be recreated. (I was surprised as I was expecting the EC2 health check to terminate them, but it does not work like that.)
My understanding is that if you stop/start an instance, your local storage is gone (as the instance might even end up in a different host), but if you just reboot the instance, it should keep the local storage.
I'm 100% sure that all providers are playing with the quantization, kv cache and other parameters of the models to be able to serve the demand. One of the biggest advantage of running a local model is that you get predictable behavior.
Yesterday GPT 5.2 wrote a python function for me that had the import in the middle of the code, for no reason. (It was a simple import of requests module in a REST client...)
Claude I agree is a lot better for backend,Gemini is very good for frontend
You don't need hundreds of services.
Give me virtual machines, reliable block storage, file storage and object storage, networking, dns, managed kubernetes, and it will cover the majority of workloads in Europe that run on Openshift or Openstack today.
Sure, EBS or any network-attached storage is expected to be a lot slower than a local SSD for synchronous writes or random reads, as there is a network stack in between. But my understanding is that for those usecases, you can use metal instances with local nvme. (ephemeral though)
I guess an important piece (conveniently left out of this story) is that it does not work if there are other cars on the road, as these cars quickly invalidate the data coming from the slow cart.