Containers + Dapr vs Functions as a Service 

If you're trying to decide between containers or Functions as a Service (FaaS) for your next web app or API, the question is when is the added complexity of a container-based architecture worth the effort compared to an FaaS approach?
There are at least 8 facets that favor containers over FaaS:
1) Portability
2) Multi-Cloud Support
3) Long Running Application Logic
4) Persistent or Consistent Throughput Workloads
5) Memory or Compute Intensive Workloads
6) Legacy Apps or Lift and Shift Scenarios
7) Broader Programming Language Support
8) Simplified Ops...In Some Cases
Check out my thoughts on each of these and share your own comments, ideas, and experiences with containers versus FaaS.
Links:
- Gergor Hohpe's articles on FaaS: www.enterprise...
- Dapr: dapr.io
- eShopOnDapr Github project: github.com/dot...
- Dapr building blocks: docs.dapr.io/d...
- Dapr bindings: docs.dapr.io/r...
- AWS Lambda quotas: docs.aws.amazo...
- Azure Functions limits: docs.microsoft...
- Google Cloud Functions limits: cloud.google.c...
- Azure Supported Languages: docs.microsoft...
- AWS Lambda supported runtimes: docs.aws.amazo...
- Google Cloud Functions supported runtimes: cloud.google.c...
Transcript:
- charliedigital...