How are you doing automated testing on this? Unit tests and Integration? If you're splitting out the GET / PUT / DELETE / etc - those still need to be tested. In a lambda that would be simple unit tests - how does it get tested in a step function?
Just came around here after looking into a giant black hole of a workflow, where analyzing all state transitions is super painfull. Will look into data preserver pattern thx :)
Well, actually it is not hard to have one codebase to run in both Lambda and Container. #!/bin/bash # Assuming "index.js" exports a function named "handler," Adjust the required path as necessary to match your project structure node -e "const { handler } = require('./index'); handler()." From here on, u can tweak that Shell script as well and simulate lambda call by passing parameters to handle that you would be extracting from env variables once u start your task :)
This two part series is very useful - especially the patterns. Love the channel!
Glad you like them!
How are you doing automated testing on this? Unit tests and Integration? If you're splitting out the GET / PUT / DELETE / etc - those still need to be tested. In a lambda that would be simple unit tests - how does it get tested in a step function?
Just came around here after looking into a giant black hole of a workflow, where analyzing all state transitions is super painfull. Will look into data preserver pattern thx :)
Well, actually it is not hard to have one codebase to run in both Lambda and Container.
#!/bin/bash
# Assuming "index.js" exports a function named "handler," Adjust the required path as necessary to match your project structure
node -e "const { handler } = require('./index'); handler()."
From here on, u can tweak that Shell script as well and simulate lambda call by passing parameters to handle that you would be extracting from env variables once u start your task :)