This is the first time I see such a simple description of this. Often you've got the feeling of "magicians" using technobabble to let things look much more difficult or new than they are.
If you're pushing a blog out - Great!
If you're pushing out anything that relies on application state... much less great.
At best, you then end up in a world of trouble dealing with eventually consistent data, sharding/tenanting, CRDTs, "edge" KV stores (that are really just hiding the eventually consistent nature from you) and all sorts of other trade offs.
If I'm directly collaborating with some half way around the globe in a web application - there is literally no magic way to wave a wand and make that latency go away.
CRDTs don't solve the semantic issue of a conflict, but nothing ever will, because the semantics are defined by business requirements, right?
Isn't the idea behind CRDTs to develop a set of "primitives" upon which one can build conflict free data structures?
And isn't all the hype about CRDTs a result of the fact that providing those primitives in a serverless way (ie, without requiring a central authority) was a hitherto unsolved problem?
Just one of the ways people work to keep salaries up ;)
I get a bigger paycheck by explaining tech to business in business terms so I'm not sure that's a valid approach after a particular level of salary.