[pwinnski]

The serverless dev experience was delightful! I'd work on a single lambda, or maybe a "stack" of related lambdas, and each was focused and lean. A serverless approach is also probably-necessarily a microservices approach, which removes a lot of complication.

It was in EdTech, so we had students downloading assignments, uploading results (lambda-fronted S3 for blob storage, DynamoDB for data), administrators paging through result, grading things, students uploading images and videos of themselves, administrators reviewing them, many lambdas being triggered by changes to S3 or DynamoDB tables, or SNS messages sent from other lambdas.

I don't think most people would consider it especially bursty, except in the most general sense around midterms and finals, but in truth even a "heavy user" is only hitting APIs every so many seconds at most, and like I said, AWS lambda bills at the millisecond level.

[pranabgohain]

Couldn't agree more on the experience of developing on serverless. And you're quite on point, about the need for a good architect who can solve most of these issues.

I know a lot of EdTech startups who are primarily serverless at massive scale.

Along with a DevOps team, an Observability tool like KloudMate will go a long way in managing serverless stacks.

[pwinnski]

I will say, if you don't have a great architect at the top level, and support from DevOps, you end up with miserable experiences like the negative stuff I see here.

Well, some of it seems to be assumptions, but I believe the negative experiences, I just think they lacked a great architect.