This question evaluates skills in designing a distributed configuration and subscription service, covering API design, real-time notification semantics (delivery and ordering guarantees), versioning, concurrency and thread-safety, durability and recovery, multi-tenant isolation, security, and scalability concerns.
Design a multi-tenant configuration service that stores key–value configuration and lets applications subscribe to changes for specific keys or namespaces (prefixes). When a value changes, subscribers must be notified promptly and reliably.
Assume namespaces are path-like prefixes (for example, /env/prod/serviceA/). Specify assumptions as needed.
Login required