Our use cases were on very well built websites and platforms. Just to give you an example:
- Redirects: We have several clients in the tech industry who host their docs and pages on Github pages. Github pages doesn't support 301s. This allowed us to both create 301s correctly and have a more manageable 301 platform for the non-development team.
- A/B testing through ghosting: A very large e-commerce client of ours wanted to run A/B test by ghosting (not to change URL) and slow roll out of the new platform. Through this they could chose which URL's were on the new platform and which ones on the old one and slowly rolled it all out.
In the future you will also be able to create pipelines so that there is a better management and audit process for bigger firms with security protocols around.
So, there are more benefits to this than just "When it's not practical to make the changes at the origin server". Infact if you are just "patching" then it's trouble.
- Redirects: We have several clients in the tech industry who host their docs and pages on Github pages. Github pages doesn't support 301s. This allowed us to both create 301s correctly and have a more manageable 301 platform for the non-development team.
- A/B testing through ghosting: A very large e-commerce client of ours wanted to run A/B test by ghosting (not to change URL) and slow roll out of the new platform. Through this they could chose which URL's were on the new platform and which ones on the old one and slowly rolled it all out.
In the future you will also be able to create pipelines so that there is a better management and audit process for bigger firms with security protocols around.
So, there are more benefits to this than just "When it's not practical to make the changes at the origin server". Infact if you are just "patching" then it's trouble.