I think this really boils down to: 1) Have an api gateway (for them, graphql). 2) Store state in a (most likely distributed) store. 3) Have services inte

I think this really boils down to: 1) Have an api gateway (for them, graphql). 2) Store state in a (most likely distributed) store. 3) Have services interact with state via an event system. All this really says is make your applications stateless. This is a trend that has been going on for a while. I don't think GraphQL nor serverless is required and are just specific to their implementation. Unless I totally missed what they were going for.