> but what you are looking for already exists I'd say, and is Fargate. No, Fargate isn’t that at all. Google Cloud Run is what you meant to say. This is of course still valuable to allow container-based workflows to…
> you can run any container (<10 GB), but it just has to implement the Lambda Runtime API[1] So in other words, you can’t run any container. Again, the entire point of containers is portability across execution…
> but you still need to code them for the event model, have a handler, etc. >It's a big improvement, but its not "run any container in Lambda". Well that’s... incredibly disappointing and makes this announcement much…
What’s the problem with this? Anything that’s scalable is “just an abstraction” on top of a heap of shards/processes/nodes/data centers/whatever.
The PHD is always updated first, long before the global status page is updated. Every single one of my clients that use AWS got updates on the PHD literally hours before the status page was even showing any issues,…
> but what you are looking for already exists I'd say, and is Fargate. No, Fargate isn’t that at all. Google Cloud Run is what you meant to say. This is of course still valuable to allow container-based workflows to…
> you can run any container (<10 GB), but it just has to implement the Lambda Runtime API[1] So in other words, you can’t run any container. Again, the entire point of containers is portability across execution…
> but you still need to code them for the event model, have a handler, etc. >It's a big improvement, but its not "run any container in Lambda". Well that’s... incredibly disappointing and makes this announcement much…
What’s the problem with this? Anything that’s scalable is “just an abstraction” on top of a heap of shards/processes/nodes/data centers/whatever.
The PHD is always updated first, long before the global status page is updated. Every single one of my clients that use AWS got updates on the PHD literally hours before the status page was even showing any issues,…