markusthoemmes

5 ms·

1.
by markusthoemmes 7y ago
Love it!
2.
by markusthoemmes 8y ago
The serverless.com framework is built around existing serverless/faas platforms and allows you to write vendor-agnostic functions and deploy them exchangeably. It does not provide the resources to run your code. it abstracts away diffe
3.
by markusthoemmes 8y ago
This of course needs to be discussed in the broader OpenWhisk community first, but taking dewitt's answer here into perspective ( https://news.ycombinator.com/item?id=17604185 ) and also based on what IBM has put out in
4.
by markusthoemmes 8y ago
Even better! Knative will allow you to even scale your containers out-of-band if you know that something BIG will happen. See https://github.com/knative/serving/issues/1656 for the discussion.
5.
by markusthoemmes 8y ago
Some of the attributes of serverless workloads will require changes deeper down in the stack (read Kubernetes). For instance constantly getting containers up or throwing them away at high rates stresses parts of Kubernetes more than its use
6.
by markusthoemmes 8y ago
If AWS EKS gives you access to kubectl or similar, it is probably trivial to setup. There shouldn't be any obvious roadblocks. Will be a great contribution to add to the guides!
7.
by markusthoemmes 8y ago
Joining in, Markus from IBM and OpenWhisk. Been involved with knative for quite some time now as well. Happy to answer any questions that might arise as well. Answers might be biased and opinions are my own. See IBM's statement: https
8.
Squeezing the milliseconds: How to make serverless platforms blazing fast(medium.com)
1 points by markusthoemmes 9y ago|0 comments