This particular article basically uses Edge Computing as a synonym for client-side computing. I've more commonly seen the phrase Edge Computing used in a differ

This particular article basically uses Edge Computing as a synonym for client-side computing. I've more commonly seen the phrase Edge Computing used in a different and more interesting way. Basically, a typical web app architecture would have servers for dynamic content in 2 or 3 places, mainly for redundancy, and use a CDN to distribute static content. The CDN in this case is the Edge, but there's no compute: just caching of static assets. That's not a great fit for some applications (those with high bandwidth or low latency requirements on dynamic data especially), but there's not really been provider support for that, so if you wanted to do it you had to deal with your own hardware in a large number of locations. If a cloud provider adds Compute to the Edge (ie Lambda@Edge from AWS, Cloudflare Workers), this architecture becomes doable for small shops.