re: Continuous Delivery Patterns with Serverless Applications VIEW POST


Here are some situations:

  • You're unfamiliar with observability and monitoring challenges that come with an entirely event-based system
  • Latency / cold start is an issue
  • You plan to ship an on-promise version of the product
  • The functionality that you're building can't be broken down into single, easily composable functions
  • Language / stack you want to use is not supported
  • You need a long running task that you can’t split into multiple smaller ones
code of conduct - report abuse