Running extension and notification module in AWS Lambda about adyen-commercetools

[zackpollard]

@LEQADA We are currently halfway through the implementation of this. What we were envisioning is that the lambda will be invoked and things such as ensureResources will run on the first cold start of the lambda, but won't run on following invocations (for that instance of the lambda). We have currently abstracted the logic out of the payment controller and into a payment handler, the payment controller will then just map the HTTP request to what the payment handler expects, and the lambda will have a similar class doing the same thing. We should have a PR ready sometime next week I imagine, I can create a draft PR for now if you would like to keep track of the ongoing work that we are doing. This is just for the extension module right now, but we will do much of the same work over in the notification module once we are done with the extension.

[zackpollard]

Both of these modules now support running inside a lambda, so i'm going to close this issue 😃

[LEQADA]

Sounds good! No need for a draft. Thank you again for initiative. 🙂

[zackpollard]

Following from conversations we have had, we are now looking at picking up this piece of work. Is this alright with your team and have you got any input into the way you would prefer this to be built before we go ahead and do the work? We are going to start looking into how we would do this today as it is now a priority for us.

[LEQADA]

Thank you for the issue @zackpollard. It's a good idea to make it serverless.
Could you share the concept of how you see the integration in a serverless environment?