middy VS pocketbase

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.

It's an obvious question, but have you looked into Pocketbase?

https://github.com/pocketbase/pocketbase

I'd like to plug PocketBase [0] for a similar use case.

Last week I was looking for a place to store random data with API access, and was looking at making a Google Sheets backend, but PocketBase was easy and didn't have a 60 rpm quota.

Deploying to a cheap VPS was very easy with CapRover.

[0] https://pocketbase.io/

What is Pocketbase? Pocketbase is an open-source backend solution offering a real-time database, file storage, and seamless user authentication with OAuth integration, all readily available right out of the box.

Browsing HN, GitHub and the like we get to see a huge variety of software products and code bases.

I often see products and think - if this product X, got together with Y, it would be pretty cool - kind of like if they had a kid together.

Not too literally, but more on the conceptual level - my level of programming is low.

E.g. Just some....

- pocketable.io & datasette (+with some more charting) [https://pocketbase.io, https://datasette.io]

I'm working on a personal project and found myself looking for an alternative to Postman/Insomnia this morning. This made me realize i've been using the same tools for so long for work (mobile development, finance) that this project may be a good time to try out some new things.

Here are a few tools that i've been using lately that I really enjoy:

https://pocketbase.io/ - A dead-simple self-hosted firebase/supabase-like "backend in a box" using golang and sqlite. So far i've been really impressed. I've gone the route of extending the base offering with more go code and am really enjoying the experience.

https://excalidraw.com/ - An open source whiteboarding tool. Slick to use and after learning some keybinds I've gotten pretty fast at throwing together diagrams to explain things to people on my team. The killer piece though is that the filetype is just json, so I can source control my diagrams. Even better, their "export to png" function has a box to embed the json data _into_ the png, allowing me to slap the diagram in places that only accept images (think confluence) and still be able to change the diagram later if needed. 10/10.

https://docs.gitlab.com/ee/ci/ - Gitlab's CI/CD toolset is really impressive, and I've gotten really intimate with it's deeper features over the past year. I'd be curious though to hear from someone who's familiar with it vs it's competitors.

Is there an article somewhere, outside of the Pocketbase docs, presenting that pattern?

- https://github.com/pocketbase/pocketbase/blob/master/core/ap...