TLDR
Serverless can be considered an enabler for many of those useful practices. It encourages components that do one thing well in a serverless world. With serverless, you are literally forced to make your components small. It also requires that you define all resources needed for the execution of your function or container. This means you cannot rely on any pre-configured state — you need to specify all. dependencies and any configuration that you must run. Here’s how serverless encourages “useful” engineering practices.via the TL;DR App
no story
Written by taavi-rehemagi | CEO of Dashbird. 13y experience as a software developer & 5y of building Serverless applications.
