Crazylychee opened a new issue, #308: URL: https://github.com/apache/rocketmq-dashboard/issues/308
Hi RocketMQ Community: As our ecosystem continues to evolve, the RocketMQ management interface plays an increasingly crucial role in usability, operational efficiency, and feature adoption. However, our current management interface project faces several challenges that limit its effectiveness and hinder our ability to leverage new RocketMQ capabilities. What problems does our current project have? * The current frontend libraries are outdated and no longer maintained, leading to poor functionality and usability. Additionally, the lack of separation between frontend and backend results in a suboptimal development experience. * The user experience is subpar, with numerous minor usability issues that need to be addressed. * It does not support ACL 2.0. * Support for the 5.0 version is inadequate. These issues not only impact the efficiency of daily operations but also limit the demonstration and adoption of RocketMQ features. Over time, the cost and risk of maintenance are also increasing. What benefits would the proposed changes bring? We propose a comprehensive modernization of the RocketMQ management interface, adopting React and Ant Design as the frontend technology stack, and rebuilding the backend foundation by upgrading to modern versions of Spring Boot and JDK to ensure long-term sustainability. This transformation aims to address the current limitations and unlock future potential. Specifically, the proposed changes will bring: * Modern Technology Stack: Adopting React and Ant Design provides a more stable, maintainable, and actively supported technical foundation. Upgrading the backend to modern Spring Boot and JDK versions further enhances performance, security, and compatibility with contemporary Java ecosystems. * Enhanced Functionality: Enables the implementation of features required by the 5.0 version, particularly crucial support for ACL 2.0. * Improved User Experience: Leverages Ant Design’s components and design principles, combined with targeted usability fixes, to significantly enhance user satisfaction. * Higher Development Efficiency and Maintainability: Modern frontend frameworks generally offer better development experiences and code organization, reducing future maintenance costs. The move to modern Spring Boot and JDK also simplifies dependency management and improves developer productivity. * Better Compatibility and Scalability: Allows for better adaptation to future version updates and technological advancements, ensuring the system remains robust and adaptable. What problems does this proposal aim to solve? * Technical Debt and Maintenance Difficulties: Addresses the high maintenance costs and risks associated with using outdated, unmaintained frontend libraries. * Functional Deficiencies and Limitations: Solves the issue of insufficient functionality in the current libraries, which cannot meet business needs, especially regarding ACL 2.0 and 5.0 features. * Poor User Experience: Addresses the suboptimal user interface and interaction design leading to a negative user experience. * Compatibility Issues: Resolves inadequate support for ACL 2.0 and the 5.0 version, ensuring the project can keep pace with technological or business developments. * Security Concerns: Addresses the shortcomings in the current permission management system. To what extent should we solve this problem? We should address this problem comprehensively and completely. This means: * Complete Replacement: This should not be a patchwork fix on the old libraries but a thorough reconstruction of the user interface using React and Ant Design. * Feature Alignment: The new UI must not only fix existing issues but also implement key features of the 5.0 version, such as ACL 2.0. * Experience Optimization: Fixing usability issues should be a primary goal to ensure the new interface offers a significantly improved ease of use. * Do It Right the First Time: Since changes are necessary, we should rebuild based on a modern technology stack to avoid repeating upgrades due to technological obsolescence in the future. We plan to detail the project plan, technical selection rationale, risk assessment, and implementation roadmap in [RIP-78](https://docs.google.com/document/d/1VWtonLh2uwQ1hU3rhYwUAhw2KNi803pZMW4KJkQFoYY/edit?usp=sharing). We welcome everyone to review it and share your thoughts and suggestions in the comments below this email. Follows is Chinese version: [RIP-78](https://m0sgzrp00oj.feishu.cn/docx/DOCGdUKVcoyAUpxIQnfcghmbnFb?from=from_copylink) Please welcome to reply to this email or comment on the proposal if you have any questions or suggestions. Best regards, Yichi Xu -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: commits-unsubscr...@rocketmq.apache.org.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
