Assuming you want to expose a set of APIs, each corresponding to a single function, each API is a separate docker container? What are the performance ramifications of functions-in-docker?
IronFunctions: language agnostic open-source alternative to AWS Lambda
21–23 of 23 posts
Re: IronFunctions: language agnostic open-source alternative to AWS Lambda
#22Assuming you want to expose a set of APIs, each corresponding to a single function, each API is a separate docker container? What are the performance ramifications of functions-in-docker?
Unfortunately, Docker has a fair bit of overhead, more on that here: https://medium.com/travis-on-docker/the-overhead-of-docker-r... . That said, the overhead is probably not a big deal in a lot of cases.
And for the those cases, where it is a big deal, the next two major milestones on the roadmap aim to work around that issue, namely hot containers and streaming input. https://github.com/iron-io/functions#roadmap . Once that's in place, it should perform similar to any API.
Re: IronFunctions: language agnostic open-source alternative to AWS Lambda
#23It's not strictly speaking an alternative to AWS Lambda, because you have to run your own IronFunctions server somewhere. So you will again have to manage servers instead of being serverless. It's nice to have this platform available though.
Right, it's Lambda anywhere ... that you want to run it. But we hope/expect to see the service hosted on all clouds soon.