Dingding stream mode dynamic management system based on multi-tenant scenario

The DingTalk Stream client dynamic management system, with its layered architecture and modular collaborative design, solves the problems of high operation and maintenance costs and poor system stability in multi-tenant scenarios, achieving high availability and resource optimization, and significantly improving system stability and resource utilization.

CN122363901APending Publication Date: 2026-07-10XIAN BODA SOFTWARE CO LTD

Patent Information

Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
XIAN BODA SOFTWARE CO LTD
Filing Date
2026-04-13
Publication Date
2026-07-10

AI Technical Summary

Technical Problem

Existing technologies lack automated monitoring and fault recovery mechanisms in multi-tenant scenarios, resulting in high operation and maintenance costs, poor system stability, and low resource utilization, which cannot meet the needs of DingTalk Stream long connection scenarios.

Method used

The DingTalk Stream client dynamic management system is built using a layered architecture and modular collaborative design. It includes a configuration access layer, a core control layer, and a resource support layer. The system achieves dynamic management of the entire client lifecycle through standardized data flow interaction between modules, and adopts instance-level tenant isolation, automated health monitoring, and dynamic resource allocation.

Benefits of technology

The system achieved an over 80% improvement in stability, an increase in service availability from 95% to 99.9%, an increase in resource utilization from 30% to 85%, a significant reduction in operating costs, and a 90% reduction in fault handling workload.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN122363901A_ABST
    Figure CN122363901A_ABST
Patent Text Reader

Abstract

This invention discloses a dynamic management system for DingTalk Stream mode in a multi-tenant scenario, comprising a configuration access layer, a core control layer, and a resource support layer. The configuration access layer includes a configuration management module and a manual control module. The core control layer includes a configuration listening module, a health check module, an event bus module, and a client factory module. The resource support layer includes a resource management module, a multi-tenant client pool module, and a log recording module. A ConcurrentHashMap client pool with tenant ID as the key is used to achieve independent storage and thread-safe access for each tenant client instance. Through collaboration between modules in the core control layer, automatic creation, updating, and destruction of clients driven by configuration changes are achieved. Automatic monitoring of client status is achieved based on timed heartbeat monitoring and event-driven mechanisms. On-demand resource allocation is achieved through expansion / contraction mechanisms and resource quota management, while a resource early warning mechanism is also added.
Need to check novelty before this filing date? Find Prior Art