5 ms·

I have been interested in running a serverless setup for a while now, so I’ve been looking at different open source alternatives to AWS lambda. I considered Ope

I have been interested in running a serverless setup for a while now, so I’ve been looking at different open source alternatives to AWS lambda. I considered OpenWhisk but felt IronFunctions would be quicker to setup and easier to run. Anyone has experience deploying/using both? Would anyone that is running OpenWhisk comment on the process to get it running?

friendly_chap 9y ago
Self plug but https://github.com/1backend/1backend https://github.com/1backend/1backend literally needs just 4 docker containers to run. They are in the ReadMe, let me know what you think of it. It contains a bunch of unique features, so it's not your typical serverless platform, but the core is the same if you don't want to go crazy with the web framework like features.
- rabbah 9y ago
  It's great to see so many functions platform - in some ways it shows there's increasing interest, awareness, and adoption. The field is still quite young and there will be a lot of experimentation and exploration. There's also a difference between deploying rapidly for local development (less is better) and actually running a functions platform at scale. AWS lambda reportedly handles over 2B lambdas a day (this was a year ago). Not every platform needs that kind of scale, but it does put things in perspectives.
  - friendly_chap 9y ago
    Hi there! Thanks for the encouragement. To be fair we at 1backend don't consider the field that new at all. It's just the old PaaS concept with some twists and reworded marketing! I personally spent years building microservices platforms at various places and after years of not implementing my insights I decided now the time is right and people might adopt it given the current hype cycle =)
    - rabbah 9y ago
      Kudos. I'd agree, old ideas, new contexts. The twists matter.
thomasj 9y ago
OpenWhisk can be started using Docker Compose locally with a single command (make quickstart) using this repo: https://github.com/apache/incubator-openwhisk-devtools/tree/master/docker-compose https://github.com/apache/incubator-openwhisk-devtools/tree/... It can also be deployed on k8s with minimal effort: https://github.com/apache/incubator-openwhisk-deploy-kube https://github.com/apache/incubator-openwhisk-deploy-kube There's also instructions for using VMs as the infrastructure layer: https://github.com/apache/incubator-openwhisk#quick-start https://github.com/apache/incubator-openwhisk#quick-start If you have any issues open an issue or join us on the slack (http://openwhisk.incubator.apache.org/slack.html http://openwhisk.incubator.apache.org/slack.html). (I'm a committer on the project).
- goliatone 9y ago
  In my previous quick search I did not find the incubator-openwhisk-devtools repo, that left me with the impression that I had to run k8s which for my purposes is too heavy handed. A docker setup is more in line with my needs (run on vpc for quick side projects). thank you!
- deadwisdom 9y ago
  It would be great if they explained that anywhere in their documentation.
antoncohen 9y ago
You might be interested in [Oracle's] Fn Project, it is open source and created by the team behind IronFunctions. I think it started life as a fork of IronFunctions. It is written in Go. http://fnproject.io/ http://fnproject.io/
- rabbah 9y ago
  Indeed, the original founders of Iron.io are at Oracle. They are up to some good stuff. See https://medium.com/fnproject/8-reasons-why-we-built-the-fn-project-bcfe45c5ae63 https://medium.com/fnproject/8-reasons-why-we-built-the-fn-p...
- goliatone 9y ago
  Thank you, will check it out. It did not come up during my (rather quick) search for alternatives.
alexellisuk 9y ago
Take a look at the other options I posted. IronFunctions runs one container per request so you'd need to evaluate if that's fast enough for your purposes. They have a new "hot" mode too but I'm not sure how far they are with supporting that.. maybe Chad could comment if he's around.

friendly_chap 9y ago

Self plug but https://github.com/1backend/1backend https://github.com/1backend/1backend literally needs just 4 docker containers to run. They are in the ReadMe, let me know what you think of it. It contains a bunch of unique features, so it's not your typical serverless platform, but the core is the same if you don't want to go crazy with the web framework like features.

rabbah 9y ago
It's great to see so many functions platform - in some ways it shows there's increasing interest, awareness, and adoption. The field is still quite young and there will be a lot of experimentation and exploration. There's also a difference between deploying rapidly for local development (less is better) and actually running a functions platform at scale. AWS lambda reportedly handles over 2B lambdas a day (this was a year ago). Not every platform needs that kind of scale, but it does put things in perspectives.
- friendly_chap 9y ago
  Hi there! Thanks for the encouragement. To be fair we at 1backend don't consider the field that new at all. It's just the old PaaS concept with some twists and reworded marketing! I personally spent years building microservices platforms at various places and after years of not implementing my insights I decided now the time is right and people might adopt it given the current hype cycle =)
  - rabbah 9y ago
    Kudos. I'd agree, old ideas, new contexts. The twists matter.

thomasj 9y ago

OpenWhisk can be started using Docker Compose locally with a single command (make quickstart) using this repo: https://github.com/apache/incubator-openwhisk-devtools/tree/master/docker-compose https://github.com/apache/incubator-openwhisk-devtools/tree/... It can also be deployed on k8s with minimal effort: https://github.com/apache/incubator-openwhisk-deploy-kube https://github.com/apache/incubator-openwhisk-deploy-kube There's also instructions for using VMs as the infrastructure layer: https://github.com/apache/incubator-openwhisk#quick-start https://github.com/apache/incubator-openwhisk#quick-start If you have any issues open an issue or join us on the slack (http://openwhisk.incubator.apache.org/slack.html http://openwhisk.incubator.apache.org/slack.html). (I'm a committer on the project).

goliatone 9y ago
In my previous quick search I did not find the incubator-openwhisk-devtools repo, that left me with the impression that I had to run k8s which for my purposes is too heavy handed. A docker setup is more in line with my needs (run on vpc for quick side projects). thank you!
deadwisdom 9y ago
It would be great if they explained that anywhere in their documentation.

antoncohen 9y ago

You might be interested in [Oracle's] Fn Project, it is open source and created by the team behind IronFunctions. I think it started life as a fork of IronFunctions. It is written in Go. http://fnproject.io/ http://fnproject.io/

rabbah 9y ago
Indeed, the original founders of Iron.io are at Oracle. They are up to some good stuff. See https://medium.com/fnproject/8-reasons-why-we-built-the-fn-project-bcfe45c5ae63 https://medium.com/fnproject/8-reasons-why-we-built-the-fn-p...
goliatone 9y ago
Thank you, will check it out. It did not come up during my (rather quick) search for alternatives.

alexellisuk 9y ago

Take a look at the other options I posted. IronFunctions runs one container per request so you'd need to evaluate if that's fast enough for your purposes. They have a new "hot" mode too but I'm not sure how far they are with supporting that.. maybe Chad could comment if he's around.