Sitecore Experience Edge Features

Provides more power to CDN (Content Delivery Network) so that round-trip to XM (Content Management) or Content Hub (CH) can be reduced. This also means improved scalability since cdn is across the world near the users. Experience Edge will sit between XM / CH and CDN. Will store a copy of the latest static site / assets and serve it to cdn. 

In a traditional CMS, without Experience Edge, in spite of having a cdn, although the cdn will store a cached copy of the site, whenever there is a publish at the Sitecore end, cdn will have to reach out to the Sitecore instance, increasing the load on the Sitecore server. With Experience Edge in place, that too with two different components one for CH and XM each, this load is considerably reduced because Sitecore publish will automatically push to the respective component of Experience Edge and have it ready for the cdn. Add to this, the static site generation concept for JSS sites and the responsiveness becomes even better.

So, future Sitecore architectures must definitely involve Sitecore Experience Edge and JSS site implementation + Content Hub to store assets.

My thought: Some kind of load balancing with just the Experience Edge, if possible, will be of greater use.

API-first development for Front-end developers since they can use APIs exposed by Experience Edge rather than from XM/CH

Two flavors:

1. Sitecore Experience Edge for Content Hub: 

- GraphQL endpoint that serves asset data

- Publish content hub data / asset data to cdn to improve load speed

- Removes CH-XM connector dependency and directly serves assets from CDN

2. Sitecore Experience Edge for XM: 

- GraphQL endpoint that serves content data

- Publish static  JSS site to CDN

In future, Sitecore Experience Edge for XP: will support edge-based personalization so that end-users can benefit from blazing-speed personalized sites