effe

You could then switch to regular servers running an open source Lambda reimplementation e.g. https://github.com/siscia/effe https://github.com/atlassian/localstack etc. Just make sure you can change the URLs everywhere.

I worked on https://github.com/siscia/effe which is basically a templare where you Write Your function in go. You compile it down to a single executable and then you do whatever you want with it. I can't provide the autodeploy part though...

A little of a shameless plug, but I am the author of effe GitHub.com/siscia/effe A microservice framework. If you are worried about latency or you want lambda on your own servers it may be worth to take a look. Feedback welcome

I wrote effe with I believe is pretty close to what Iopipe want to do. You basically write your function in golang and it get compiled to a single binary that you can run everywhere. Everything is ready but the deploying, so you will need to deploy your own, but it already can create a docker container so... Everything is on github: https://github.com/siscia/effe

I was developing something similar with effe[1] e effe-tool[2], the idea is similar. You wrote your service in go following in such a way that it expose 3 function and it get compiled down to a single binary, then you can dockerize your application (images usually are smaller than 6MB) and deploy it, wherever and whenever you want. Of course everything is open source. I explained it a little better here: http://redbeardlab.tech/2016/03/05/effe.html [1]: https://github.com/siscia/effe [2]: https://github.com/siscia/effe-tool

effe - an open source implementation of AWS Lambda http://github.com/siscia/effe It is awesome because it gives,you more power than AWS Lambda and because you have a sane way to manage it via effe-tool (http://github.com/siscia/effe-tool), also it is written in go which should make it faster than competitor...

I am developing something similar with effe [1] and effe-tool [2] (completely WIP), that are suppose to be an open source implementation of AWS lambda. I am facing problems similar to the one of the author, and I can see why he made some choices but I disagree on most. In my opinion we should aim to a tool to build single executables and another tool to package those executable in a docker container. Also I am doing my best to have as little as possible configurations, configurations are needed to deploy your application, and deployment is a different kind of problem. I must say that is HARD, mainly for the constrain of go. I would love to attach metadata to a go package, configuration would became a no-issues. I would love to build my packages in a dynamic way, eg. these file is the scaffolding, those other are the custom logic, go compi