This topic explains the differences in resource management features between the console SDK and client SDK, along with usage recommendations.
Resource management
Before, resource management was handled solely by the client SDK. However, with the growing need for enterprise-level features (including fine-grained permission control, operation auditing, and API tagging), the console SDK has become the primary platform for resource management, providing more standardized administrative capabilities.
Comparison
Item | Console SDK | Client SDK |
Parameter specifications | The maximum message retention period is 7 days. All APIs will converge to this standard in the future. | The maximum message retention period is 15 days. |
Error readability | The error message logic is optimized, reducing the troubleshooting duration by over 50%. | No special handling. |
Feature evolution | Resource management capabilities are gradually carried by the console SDK. | Will focus on message sending and receiving scenarios. |
Usage recommendations
For new users or those developing new business scenarios, we highly recommend using the console SDK for resource management to take full advantage of its modern features and superior user experience.
Existing users who are still utilizing the client SDK are also encouraged to transition to the console SDK to benefit from its more comprehensive service capabilities and to mitigate compatibility risks in future updates.