Open leandrodamascena opened 1 year ago
Great idea @leandrodamascena . Though I was thinking of a nested stack scenario like here
https://github.com/aws-samples/sam-accelerate-nested-stacks-demo.
But I don't mind going either way. It'll be a great learning experience for me.
I was also thinking of expanding the project a bit and adding a Products Service/domain. So the project would have the following services/domains
What do you think? Am I missing something?
We should go a little deeper to define the best architecture for the project. We will have a frontend, several lambdas, and resources that are shared with the entire project. The current architecture defines the entire infrastructure in a single template, which forces us to update everything whenever we deploy. What do you think of dividing this by service/domain? How do you organize your SAM applications? We might get some insights from https://serverlessland.com/repos?framework=AWS+SAM
I like this project: https://github.com/aws-samples/aws-serverless-airline-booking.