Comparison of different function signatures
There’re three function signatures in OpenFunction:
OpenFunction. Let’s explain this in more detail using Go function as an example.
CloudEvent signatures can be used to create sync functions while
OpenFunction signature can be used to create both sync and async functions.
OpenFunction signature can utilize various Dapr building blocks including Bindings, Pub/sub etc to access various BaaS services that helps to create more powerful functions. (Dapr State management, Configuration will be supported soon)
|Async Functions||Not supported||Not supported||Supported|
|Dapr Binding||Not supported||Not supported||Supported|
|Dapr Pub/sub||Not supported||Not supported||Supported|
As you can see,
OpenFunction signature is the recommended function signature, and we’re working on supporting this function signature in more language runtimes.
Was this page helpful?
Glad to hear it! Please tell us how we can improve.
Sorry to hear that. Please tell us how we can improve.