Re:IronFunctions: language agnostic open-source alternative ...
by wilsonfiifi on Tuesday November 15, 2016 @11:56PM
(#12964626)
This is absolutely fab! I've been trying to figure out an elegant way to 'pipe' query results to user defined filter functions[0] for my side-project[1]. Can't wait to give this a go and dig into it. Thanks for making this open source and writing it in Go(lang) :-D
Re:IronFunctions: language agnostic open-source alternative ...
by kennu on Wednesday November 16, 2016 @12:49PM
(#12969437)
It'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.
Re:IronFunctions: language agnostic open-source alternative ...
by kaishiro on Tuesday November 15, 2016 @04:37PM
(#12962459)
Woah, this is a big deal.
I played with IronWorkers a lot and even built some tooling around spinning up a worker and long polling an IronCache waiting for output (yes, it was a little gnarly). I'm really excited to play with this.
Re:IronFunctions: language agnostic open-source alternative ...
by fierro on Wednesday November 16, 2016 @12:50PM
(#12969445)
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?
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 ...
by carimura on Tuesday November 15, 2016 @02:59PM
(#12961617)
IronWorker is more classic job processing whereas IronFunctions is AWS Lambda-style sync service. We'll follow up with a longer blog post on the differences.
Re:IronFunctions: language agnostic open-source alternative ...
by treeder on Tuesday November 15, 2016 @02:32PM
(#12961377)
Yes, Java is supported. Like the other comment, anything you can run in a Docker container, which is pretty much any language. It also supports the same format/structure as Lambda in Java.
It's nice to have this platform available though.
I played with IronWorkers a lot and even built some tooling around spinning up a worker and long polling an IronCache waiting for output (yes, it was a little gnarly). I'm really excited to play with this.
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.
It does work also with Java lambda apps, you can import them straight from AWS Lambda API using the CLI app.