Design and Implementation of a Unified Permission Management Service (MPS)
This article details the design and development of a unified permission management service (MPS) that consolidates RBAC, ACL, and DAC models to solve fragmented enterprise permission issues, covering requirement analysis, technical selection, functional modules, deployment, and performance outcomes.
In the era of rapid IT development, many enterprise platforms have fragmented permission systems, leading to chaos and unclear hierarchies.
The Unified Permission Management Service (MPS) was designed to integrate permissions across Baidu's data middle‑platform, combining RBAC, ACL, and DAC models.
Requirement analysis identified needs such as platform integration, hierarchical role definition, unified authentication, approval workflow, and API design.
Technical selection chose Baidu's internal Go Development Platform (GDP) for its infrastructure support, configurability, RPC capabilities, and Prometheus‑based monitoring.
The permission model separates business permissions and management permissions, applying ACL for fine‑grained resource control, DAC for owner‑driven delegation, and RBAC for role‑based scalability.
MPS is divided into four functional modules: Platform & Node Management, Permission Management, Application & Authorization, and Permission Audit & Recovery, each providing features like node synchronization (push/pull), online request and approval, automatic revocation, and audit logging.
Deployment in production serves nearly 40 business platforms, managing over 100 000 permission nodes, handling thousands of daily requests and up to 1.3 million API calls per day, demonstrating the system’s reliability and scalability.
Architect
Professional architect sharing high‑quality architecture insights. Topics include high‑availability, high‑performance, high‑stability architectures, big data, machine learning, Java, system and distributed architecture, AI, and practical large‑scale architecture case studies. Open to ideas‑driven architects who enjoy sharing and learning.
How this landed with the community
Was this worth your time?
0 Comments
Thoughtful readers leave field notes, pushback, and hard-won operational detail here.