|
|
|
|
|
by huksley
1321 days ago
|
|
A lot was said good about serverless, and I was a big proponent of going ”all in”, but now as CTO of small startup I am careful with it. From my experience of 4 years with serverless in AWS following problems have been identified: - Difficult to debug - Difficult to collect logs - Lambda@Edge - Slow cold starts - Frontend and NodeJS bundling are problematic - size limits, slow and unpredictable problems - Pricing are difficult to estimate - Careful planning needed for network and architecture - how lambdas work together - Workflow orchestration might be needed What is serverless good for? - Queue processing - Event processing - Internal infrastructure code |
|