Tech
Everything we got wrong caching a multi-tenant SaaS on one domain
Every page we serve falls into one of four buckets, and they want opposite things from a cache:
Marketing pages never change between deploys.
Blog articles change when someone hits publish in the CMS.
Tenant storefronts change when a seller edits a product — and must never be cached for the seller themselves.
The logged-in app must never be cached at all.
The obvious move is to split them: blog.grouptizer.com , stores.grouptizer.com , app.grouptizer.com . Separate ...
Read the full discussion on Dev.to
This article was aggregated from Dev.to. Click to join the conversation.
View on Dev.to