Best practices for building Serverless apps
Best practices for building Serverless apps
Hi all, I'm one of the authors of Serverless-Stack.com — an open source guide to building full-stack apps with AWS Lambda and React. Since it's launch in 2017, it's become one of the most widely read guides for building Serverless apps. Today we are adding a new section to the guide that walks you through the best practices of building large Serverless applications. It tries to address some of the most common questions that teams have: - How should my project be structured when I have dozens of interdependent services? - How should I manage my environments? - What are the best practice for storing secrets? - How do I make sure my production environments are completely secure? - What does the workflow look like for the developers on my team? - How do I debug large Serverless applications? The guide is very comprehensive and we go through it step-by-step: https://serverless-stack.com/chapters/best-practices-for-building-serverless-apps.html I hope you find it helpful and let me know if there is something else we should cover.
Share cardActual performance
Launch Intel predictions
Analyze your own launch →Correct prediction on native model
Similar products
Serverless GraphQL
Go DDOS Yourself (serverless-artillery)
FaaS-netes – Porting Serverless FaaS to K8s
OpenFaaS accelerates serverless Java functions
Serverless on Rancher/cattle with faas-rancher
Integrating Serverless OpenFaas with GraphQL
Serverless sorcery with ImageMagick
Going Serverless
Canary deployments on Serverless
Shortly, a serverless pastebin