DD only supports lambda.Start() which limits some of the functionality and uses of lambda. The difference between lambda.Start() and lambda.StartHandler() is that the former takes care of the serialization while the second operates and returns a []byte and accepts a struct that impliments Invoke()
For teams that have many lambdas that implement lambda.StartHandler() the lift to use DD is harder than if DD just supported that call behavior as well its an easier transition for teams.
Hi @zbintliff I've just released 1.1.0 which adds the 'WrapLambdaHandlerInterface' method, which can be passed to StartHandler. Let me know if that addresses your use case.
Expected Behavior
DD only supports
lambda.Start()
which limits some of the functionality and uses of lambda. The difference betweenlambda.Start()
andlambda.StartHandler()
is that the former takes care of the serialization while the second operates and returns a[]byte
and accepts a struct that implimentsInvoke()
For teams that have many lambdas that implement
lambda.StartHandler()
the lift to use DD is harder than if DD just supported that call behavior as well its an easier transition for teams.