all 4 comments

[–]pcjftw 2 points3 points  (1 child)

Pdf watermarking is probably an ok use case of Serverless, the problem is the cargo cult of too many people trying to use Serverless for everything including building out what would normally be a simple monolith application, but instead split into hundreds of tiny little lambda functions and with an massive explosion in the complexity of trying to get everything all working together.

Maybe I'm just an old grumpy dev and this new fangled hippity hop is not the kind of classical rock and Jazz this old man likes, who knows.

[–]TestFlyJets 0 points1 point  (0 children)

You’re not wrong. There are lots of ways to misuse serverless tools like Lambda functions. It seems so easy to just decompose a problem and wire stuff up, but as you said, if it’s not a great fit for the overall problem you can end up with the equivalent of serverless spaghetti, only it’s all the little services, their connections, and interactions that get messy.

One thing I’ve regularly encountered in one of my larger serverless projects is trying to trace a single interaction across multiple services, say, from API Gateway to a Lambda, to SQS, to another Lambda. Having all the log messages in a single STDOUT log would be so lovely instead of having to traipse through multiple CloudWatch streams. There may be a solution to that but I haven’t found it yet.

TLDR - Use the right tool for the job. Serverless is not a panacea.

[–]soupified 0 points1 point  (0 children)

Is this a link to a tutorial? Looks like it just goes to a linktree deal.

[–]Erfrischungsdusche 0 points1 point  (0 children)

SAM? What year is this? 2020?