Integration / Apache Pulsar Interview questions
Why is Pulsar considered multi-tenant by design?
Multi-tenancy is built directly into Pulsar's naming hierarchy (tenant to namespace to topic) rather than layered on as a convention, so isolation and policy boundaries exist at the platform level from the start.
Each tenant can have its own authentication and authorization rules, and each namespace within a tenant can carry its own retention, replication, and quota policies - letting one shared physical cluster safely host many independent teams or applications.
This differs from systems where isolation is achieved only through naming conventions or separate clusters per team, which pushes governance work onto operators instead of the platform itself.
Multi-tenancy in Pulsar is enforced through:
Namespace-level policies can differ:
More Related questions...
