0 views collected around this technical thread.
This article explains how to build a flexible, scalable permission control system in Java using custom annotations and Spring AOP, covering basic concepts, system requirements analysis, database schema design, annotation definitions, aspect implementation, and business logic services for comprehensive access management.
This article presents a comprehensive overview of NIO's company‑wide knowledge platform, detailing its background, layered architecture, retrieval‑augmented generation workflow, challenges such as accuracy, permission control and high concurrency, and future plans for AI‑assisted understanding, creation, multimodal capabilities, and expanded knowledge types.
The ABF Platform Configuration Center serves as a factory‑style, configuration‑driven middle‑office development system that unifies application, page, permission, layout, and custom extensions, allowing nearly 100 % reuse of rendering functions and rapid, standardized creation of internal business applications.
The article explains how permission control in a front‑back separation architecture defines resources and permissions, outlines the distinct responsibilities of frontend and backend in enforcing access, and provides practical implementation examples with component tags and Java interceptor code.
This article explains how permission control is re‑designed for front‑end/back‑end separated applications, defining resources and permissions, outlining the distinct responsibilities of front‑end routing and component rendering versus back‑end API validation, and providing practical implementation examples in React and Java.
The 2020 Weimeng incident, caused by a malicious VPN‑based intrusion that deleted production databases, exposed massive financial loss, damaged corporate reputation, and highlighted critical gaps in permission control, backup strategies, legal compliance, and security awareness for modern operations teams.
This article explains how permission control is re‑thought for front‑end/back‑end separated systems, defining resources and permissions, outlining the distinct responsibilities of the front‑end and back‑end, and providing concrete implementation examples with component‑level checks and server‑side interceptors.
This article explains how Qunar tackled growing network device management workload, low‑efficiency manual processes, and operational risk by designing an integrated platform that automates common tasks, enforces permission‑based controls, records audits, and provides real‑time monitoring and scalable data collection.
Facing growing network device counts and limited netops staff, Qunar built a network device operations platform that integrates command automation, permission-controlled tasks, monitoring, and dynamic scaling using Docker, Marathon, and Celery, thereby improving efficiency, reducing risk, and enabling comprehensive auditability.