4 ms·
Yes, and no. on the one hand lambda means that you almost nothing in view between you and an HTTP endpoint. However, a lot of "cloud engineering" is based on
by KaiserPro 3y ago
Yes, and no.
on the one hand lambda means that you almost nothing in view between you and an HTTP endpoint.
However, a lot of "cloud engineering" is based on two limitations that were inherent to AWS:
1) no machine migration (ie the ability to move a VM to a new host without downtime)
2) No large scale posix file system.
this forced people for good or ill to push lots of things to s3 (a slow, inflexible but ultimately easy enough for 70% of cases). It also meant that people started to go batshit for storing state in unusual ways. Allowing for recovery when having to rebuild machines.
Has EC2 had some of the features that VMware had at the time (I suspect xen had it too, but it was too hard to scale or secure) the world would look more like mainframes, rather than "cloud".
- dijit 3y agoStart looking at Google cloud. They have VM migration built in and it's transparent as heck. Basically seamless. You might miss a single packet (in my observed experience). This was one of the main reasons I chose them. They also have managed NFS, but I can't speak to the quality as I've never used it: https://cloud.google.com/architecture/partners/netapp-cloud-volumes/creating-nfs-volumes https://cloud.google.com/architecture/partners/netapp-cloud-...
- KaiserPro 3y agoIts always been possible, its just AWS offered something good enough first. its a lesson for us in programming when AI starts to automate large parts of it. Being techincally the best is nothing when you can replace slow hard to build things with shitter but significantly faster to deploy things.