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<p><pre><code> [0] https://bytengine.readthedocs.io/en/latest/funcs.html
[1] https://github.com/johnwilson/bytengine</code></pre>
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.<p>It's nice to have this platform available though.
Woah, this is a big deal.<p>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.
also join the real-time conversation: <a href="http://get.iron.io/open-slack" rel="nofollow">http://get.iron.io/open-slack</a>
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?