mikebroberts

Hi Mike,

Article author here. Don't worry, I'll be laying on some cold, hard, reality later in the series. I definitely don't encourage SPAs universally and I'll be talking extensively about the concerns of handing over responsibility to vendors.

Welcome to Old Developers Club. :)

There's definitely a performance tradeoff, one which I reference a little in the latest part and will definitely talk about more when I get to drawbacks (likely in the 5th update.) There's definitely a big class of applications where FaaS with its current limitations isn't a good choice, but I wouldn't say that class is universal.

12 factor statelessness I read as meaning more application / domain state rather than infrastructure state btw.

If you are able to do that you would have my appreciation as the article author! :)

The latest installment just went live - conveniently I offer a comparison to PaaS in it (in that I think there are significant differences between PaaS and FaaS)

Thanks - yes the 'serverless' name isn't great, especially without the clarification of 'server-application-less', which was one of the drivers to me writing the article. I'm not in love with FaaS as a name (yet another AAS), but it's certainly more descriptive than serverless.

Hi, this article was actually written by me, @mikebroberts, but Martin graciously asked if I could host on his site. I don't work for ThoughtWorks but did a decade ago.