I said REST API backend not GraphQL though. Also wasn't your conclusion to not use Lambda with stable high traffic needs like, say, a website? I think a lot of people use Api Gateway to do exactly that
Websites are often more stable than bursty, unlike with some batch/report service. What is your definition of high-traffic then, if your conclusion is that Lambda is okay as a BFF REST API backend for websites? What else is stable "high-traffic" as an anthesis to burst?
Comments
https://youtu.be/LBMDewzMShE
stable is the anthesis to burst
but what qualifies as "high-traffic" means different things to different people
they have a small team, they wanna move fast, and have no specialist ops person, so Lambda is better in total cost of ownership (TCO) terms