3 ms·
I still remember the absolute shock GAE was to me. Back in 2006, for a lot of people when you wanted to run a service, you configured your own LAMP server. Onc
by Jyaif 8y ago
I still remember the absolute shock GAE was to me.
Back in 2006, for a lot of people when you wanted to run a service, you configured your own LAMP server.
Once everything was running, you didn't touch it and hoped there was not going to be a power failure.
Then GAE came and for the first time you got security updates, uptime, and automatic scaling without having a dedicated sysadmin.
Needless to say that I've been a customer and advocate of this service from the beginning.
My oldest service is still running. I just had to update a .yaml file twice... in a decade.
It's kind of sad the amount of people that are wasting their time administrating their own servers when it could be done automatically. I suspect the hype around k8s will waste millennia of man-power.
- trhway 8y ago>the hype around k8s will waste millennia of man-power. k8s and serverless are different things. They are different layers of the stack. K8s is just an OS spanning multiple machines (more specifically process management layer which makes it look like we dealing with such an OS when it comes to process management). A scalable serverless implementation needs something like k8s or some similar process management layer under it.
- deleted 8y ago[deleted]
- iampims 8y agoSame, I’ve had a single service run (almost) unchanged since 2009… it just works.
- outworlder 8y ago> It's kind of sad the amount of people that are wasting their time administrating their own servers when it could be done automatically. It is, provided your service fits GAE's limitations. If it does, great! Otherwise, you are out of luck. People are running a lot more workloads than LAMP servers.
- jgeraert 8y agoI guess the same goes for Lambda.