missing composability demonstration

[eladb]

Instead of ad hoc functions for "wrapping a lambda with a hit counter", I rather we show what it looks like in Go to define a reusable construct that can be then shared and composed together into higher level components. This is an important part of the CDK and we are missing it.

aws-cdk-go/examples/workshop_102_writing_constructs/main.go

Line 36 in 463092a

func WrapLambdaWithHitCounter(stack cdk.StackIface, id string, downstreamFn awslambda.FunctionIface) *awslambda.Function {

[jasdel]

Thanks, Could you describe more about creating a reusable construct? I'd like to understand the difference more. In the WrapLambdaHitCounter func of the example, it returns a composed lambda function construct, (awslambda.Function). This example function could be used by users to add any hit counter as Lambda middle ware to their stack. Of course a real world usage of this would most likely be different based on use case, such as having configuration passed in specific to how the hit counter is configured, such as the table name used.

Also it would be very helpful if you could describe the functionality that is missing. I think that will help evaluate this issue more.