qldb-simple-demo VS middy

To try this out yourself, check out the backend folder in qldb simple demo on GitHub.

The full source code can be found at QLDB Simple Demo, but lets walk through the main steps involved.

For those of you that want to take a look at the CDC Outbox style pattern with QLDB and Kinesis, Matthew Lewis has created a demo available on github which highlights this process. It is also available as a running reference example that you can play around with at demo.qldbguide.com.

In many cases, you will have to write the same authorization code in multiple functions. For example, you might want to check that the user is in the requested organization. You can share this code in a middleware. If you are using AWS Lambda, you can rely on middy.

Adding the is-test flag to our object metadata gave us our way of passing some kind of test context into our workload. The next step was to make the Lambda Function capable of discovering the context and then using that to control how it behaves under test. For this we used Middy.

I also decided to use the middy library to add CORS management to our lambda function. This will allow us to call our lambda function from our frontend, without having to worry about CORS.

Is there any equivalent to Node based https://middy.js.org/ for Golang?

And if your requirements were to change at a later date, it’s straightforward to swap out SSM Parameter Store with Secrets Manager there and then. Especially if you’re accessing the relevant service through a middleware layer such as Middy for javascript Lambda functions.

This function uses the Middy middleware engine to handle unhandled errors and add CORS headers in the response.

I mean I'm literally building an AWS lambda function that outputs HTML when it's called via API Gateway. So someone hits https://mydomain.com/mycoolpage, then the MyCoolPage AWS Lambda function is executed and outputs whatever.

If you're interested, I use https://middy.js.org/ as a middleware engine for my AWS lambda functions which I find helpful.

I use the open sourced serverless framework for doing deploys https://www.serverless.com/

middy for lambda-side middleware

That is it from the CDK side. Now let us create the handler and retrieve that secret. I like to use middy which describes itself as "stylish Node.js middleware engine for AWS Lambda". It offers some helpful middlewares like ssm which will help us retrieve and cache values from SSM Parameter Store. (Middy provides various other official middlewares including one for Secrets Manager.) I prefer a middleware for this because it keeps the code for retrieving the secret out of your handler which should deal with actual business logic.