So polyscale is an edge-based cache for your DB. I immediately scrolled to the "Cache Invalidation" section, since that's the hard bit.
TL;DR - They also have you route your writes through Polyscale, and they watch the data being written to decide what needs to be invalidated, then it sounds like there's a fallback for complex queries that just looks at last time a table was hit.
I wonder how things like views and prepared statements work?
