This project is structured in a mono-repository where it is possible to have an end-to-end view of the project, from the front-end to the infrastructure as code using CDK. In terms of technologies, I chose to make the most of AWS resources, especially Lambda, API Gateway, DynamoDB, and S3. Casually I may delve deeper, including SQS for some events.
In this session, all the infrastructure code using CDK, where OO and precedence issues were used to build the Stack.
About the infrastructure, all the code can be seen from the ./infrastructure folder. That all resources have unit testing to check permissions and precedence.
In the API, I used NestJS to ease the application’s modularization and reduce the need to create non-functional codes with standardization. In terms of architecture, I chose to use domain-oriented CQRS, as we can explore asynchronous event invocations that can react to task stream actions. The command part is free to be executed in an HTTP controller, event, or even a lambda handler. As for the unit tests, I kept them nested in implementing modules and classes, so test contexts’ maintenance, coverage, and execution become more usual and visual.
The postman collection is in ./postaman.json, and you can test routes there.
In the API, I used NestJS to ease the application’s modularization and reduce the need to create non-functional codes with standardization.
I chose to run a full proxy inside the nest. It was just a simplification; I know in advance that in terms of performance and API design, it is more advisable to use a standalone application and directly call each function and have a handle per route. Ref
npm run buildcompile typescript to jsnpm run watchwatch for changes and compilenpm run testperform the jest unit testscdk deploydeploy this stack to your default AWS account/regioncdk diffcompare deployed stack with current statecdk synthemits the synthesized CloudFormation template