It is great to have front end and backend in different repos. But what I am imagine is that the project will entail a lot of code dealing with different pipelines and tasks that will work together in a rather asynchronous matter.
So I imagine some project structure with an app folder with a test folder. In the app folder there should be a level where the entry points for the lambda functions sit and a folder where everything else sits that get imported and re-used.
Finally, a good build folder might become quite involved if the deployment of code-changes will/should be automated in a staging and production environment etc.
This does not need to be build quite yet but it would be interesting what other people decide in terms of project structure for complex projects on Lambda.
There will be also quite a layer of credentials of different platforms, email providers, etc. That should be deployed in a manner that follows the twelve principle. Which means that build scripts will pull these out of secure storage at the latest possible time, etc. to inject them as environmental variables into the Lambda function.
Copied from @postfalk :
It is great to have front end and backend in different repos. But what I am imagine is that the project will entail a lot of code dealing with different pipelines and tasks that will work together in a rather asynchronous matter.
So I imagine some project structure with an app folder with a test folder. In the app folder there should be a level where the entry points for the lambda functions sit and a folder where everything else sits that get imported and re-used.
Finally, a good build folder might become quite involved if the deployment of code-changes will/should be automated in a staging and production environment etc.
This does not need to be build quite yet but it would be interesting what other people decide in terms of project structure for complex projects on Lambda.
There will be also quite a layer of credentials of different platforms, email providers, etc. That should be deployed in a manner that follows the twelve principle. Which means that build scripts will pull these out of secure storage at the latest possible time, etc. to inject them as environmental variables into the Lambda function.
https://12factor.net/