Visit this link to visualize the diagram.
Click here to download the Postman Collection.
- EKS Cluster IaC
- Databases IaC
- Queues & Topics IaC
- Lambda Migrator
- Microservices
- Lambda Register
- Lambda Authorizer
- Lambda Login
- API Gateway
The RIPD report can be found here.
Bellow you can find the OWASP Zap reports for the project.
Since none of the reports returned high severity issues, no fixes were applied to the project.
To view the PDF report, click here.
| Risk Level | Number of Alerts |
|---|---|
| High | 0 |
| Medium | 0 |
| Low | 2 |
| Information | 1 |
| False Positive | 0 |
To view the PDF report, click here.
| Risk Level | Number of Alerts |
|---|---|
| High | 0 |
| Medium | 0 |
| Low | 1 |
| Information | 0 |
| False Positive | 0 |
To view the PDF report, click here.
| Risk Level | Number of Alerts |
|---|---|
| High | 0 |
| Medium | 0 |
| Low | 1 |
| Information | 0 |
| False Positive | 0 |
To view the PDF report, click here.
| Risk Level | Number of Alerts |
|---|---|
| High | 0 |
| Medium | 0 |
| Low | 1 |
| Information | 0 |
| False Positive | 0 |
The SAGA pattern chosen for the project is the Choreographed Saga Pattern. This pattern was chosen because it is a good fit for the use case of the application, which is a microservices architecture. Since the project is not so big or complex, the use case is simple enough to be implemented with this pattern.
Bellow is a diagram of the SAGA pattern when the order follows the "happy path":
But when the order follows the "unhappy path", like an invalid payment, the compensation flow is used to handle the exception:
The diagram below shows the architecture of the project:
