4 ms·
My backend is all on AWS, while my frontend is on Netlify. The backend is a simple event based system. I am using Lambda (.NET Core), DynamoDB and SQS on the b
by imafish 7y ago
My backend is all on AWS, while my frontend is on Netlify.
The backend is a simple event based system. I am using Lambda (.NET Core), DynamoDB and SQS on the backend. Frontend API calls trigger Lambdas, which either schedule or create SQS messages, that fan out to a number of Lambdas. For domain management I use serverless-domain-manager which is able to create subdomains in AWS Route 53 and create mappings between CloudFront and Route 53 DNS.
I have two deploy stages, dev and prod, which automatically deploy to their separate instances and subdomains. This is all setup in a single serverless.yml file and deployed through AWS CloudFormation (which Serverless allows me to know practically nothing about and still deploy my changes).
GitLab CI/CD builds, tests and deploys my dev stage on commit to develop branch, while the prod deploy is a manual job in GitLab from the master branch. Netlify also automatically deploys the frontend on commit.
So I guess that is my tech stack :)
Edit: Also, these services are practically free until you hit a substantial amount of resource consumption.