6 ms·
I develop and maintain an app using the serverless framework. I have set up db, API gateway, functions, queues and custom domains through it and love how easy i
by imafish 7y ago
I develop and maintain an app using the serverless framework. I have set up db, API gateway, functions, queues and custom domains through it and love how easy it is to get going but also how powerful the framework has shown to be in terms of configuring the underlying services.
With that in mind - you already have a system that is highly configurable and easy to figure out - I really have a hard time figuring out what the purpose of Serverless Components is - is it mainly the sharing Components part?
- yumraj 7y agoWhat all services/db/frameworks are you using?
- imafish 7y agoMy 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.
- ac360 7y agoGood question. I responded in a separate comment regarding "Why Serverless Components?"