functions-framework

(Disclaimer: I work on Google Cloud Functions) With Google Cloud Functions, you can run your function locally using the Function Framework libraries (available in all Cloud Function languages) [0]. These libraries are used in production Cloud Functions, so you're not emulating the runtime. The feedback loop / devX is pretty simple with just 1 command to run the function locally like a library for every language. We have some guides on local development here [1]. Our samples have system tests that use the FF. You also can bundle your function in a container after building it with `pack build` [2]. This provides an exact container environment with things like environment variables and system packages. We're working on improving eventing devX, but we have some `curl` examples here [3]. Connecting multiple functions together eloquently is sti

Ah yes, good point. I neglected to cover that. Well, in a nutshell: * FunctionsFramework allows us to open-source the parts of the runtime not tied to the Google Cloud Functions hosting environment itself, meaning it should be possible to port it to other hosting, such as Kubernetes, Google Cloud Run, even FaaS products from other vendors. * Procs work, but they're just objects. We'd still need some kind of interface to name them, load them, etc. Otherwise we'd be limited to, e.g., setting a special constant or global variable to the proc, which is messy, makes testing harder, etc. * Speaking of which, a FunctionsFramework library gives us a place to put the unit testing library, tools to spin up a functions server locally for testing, and whatever tools developers might find useful in the future. For reasons such as these, Google's overa