Storing tens of thousands of articles, products, and configurations for 140+ tenant domains in a single monolithic JSON file creates severe file locking and Git merge conflicts. Our architecture partitions data into isolated domain-scoped shards (`data/posts/
1. Sharded Data Architecture Workflow
Each domain operates as an autonomous shard. When an article is updated via the CMS REST API, the system executes an optimistic dual-write: mutating the local domain JSON shard with an incremented revision record while simultaneously executing an atomic MongoDB `$set` upsert.
