3 ms·

so basically a host your own AWS Lambda? very interesting wondering if this has any of the cold boot time lags

• seangrogg 10y ago
  According to the article it has ~100ms "cold boot" times for Python and Node.js
  • brilliantcode 10y ago
    I wonder why someone would host their own aws lambda, isn't the whole point of serverless so I don't need to mess with servers?
    • defen 10y ago
      It's for when you want the benefits of serverless computing for your engineers, but your organization is too big (too many requests) for lambda to be financially feasible. Or you project things getting to that point and don't want to be locked into the AWS ecosystem.
    • snug 10y ago
      Vendor Lock-in
    • rpk09 10y ago
      I was talking to a financial company about aws lambda and they wanted control over the underlying containers/VMs that is running the aws lambda, unfortunately AWS lambda doesn't give you that control and 'fission' does
      • _Marak_ 10y ago
        You should look at https://github.com/stackvana/microcule https://github.com/stackvana/microcule
    • soamv 10y ago
      Kubernetes gets you pretty far along the path of not messing with servers (especially if you use GKE). And we think there's other advantages to Functions-as-a-Service on Kubernetes -- it simplifies the dev workflow, improves server utilization, interoperates well with other services on K8s, etc.