The *serverless-first* mindset is a pragmatic adaptation of the [[Serverless mindset]].
The ideal realisation of the serverless mindset would be a software product built entirely from [[What makes a service "serverless"|fully serverless]] services. But in reality, there will often be system use cases where dogmatically insisting that only fully-managed, self-scaling & pay-per-use services be used will result in an inferior product for the user.
The serverless-first mindset posits that a service with fully/mostly serverless attributes should be the default starting point for each system use case when designing the architecture. But if it proves that another non-serverless option will result in a better product, then that should be selected.
- [[When is serverless not a good fit]]