You can configure HTTP caching for your site on Platform.sh in several ways. Which one you should use depends on your specific use case.
You should use only one of these at a time and disable any others. Mixing them together most likely results in stale cache that can’t be cleared.
Every project includes a router instance that includes optional HTTP caching. It’s reasonably configurable and obeys HTTP cache directives, but doesn’t support push-based clearing.
If you’re uncertain what caching tool to use, start with this one. It’s enough for most uses.
Platform.sh is compatible with most commercial CDNs. If you have a Dedicated instance, it comes with the Fastly CDN.
CDNs generally offer the best performance as they’re the only option that includes multiple geographic locations. But they do tend to be the most expensive option.
Platform.sh offers a Varnish service that you can insert between the router and your app.
It has roughly the same performance as the router cache. Varnish is more configurable, but it requires you to be comfortable with Varnish Configuration Language (VCL). Platform.sh doesn’t help with VCL configuration and a misconfiguration may be difficult to debug.
Generally speaking, you should use Varnish only if your application requires push-based clearing or relies on Varnish-specific business logic.
Many web apps and frameworks include a built-in web cache layer that mimics what Varnish or the Router cache would do. Most of the time they’re slower than a dedicated caching service as they still require invoking the app server and only serve as a fallback for users that don’t have a dedicated caching service available. Generally speaking, use app-specific web cache only when it includes app-specific business logic you depend on, such as app-sensitive selective cache clearing or partial page caching.
Note that this refers only to HTTP caching. Many apps have an internal app cache for data objects and similar information. That should remain active regardless of the HTTP cache in use.
HTTP-based caching systems generally default to including cookie values in cache keys to avoid serving authenticated content to the wrong user. While this is a safe default, it means that any cookie effectively disables the cache, including mundane cookies like analytics.
The solution is to set which cookies should impact the cache and limit them to session cookies. For the router cache, see cookies in HTTP caching. For other cache systems, consult their documentation.