The Jade 2025 release focuses on modernising the developer experience and helping you build faster, smarter, and more scalable applications.
Field |
Description |
Use Case ID |
UC-ARCH-002 |
Title |
Enable and Document Primary/Secondary Database Routing (Read/Write Split) |
User Role |
Solution Architect / Developer |
Description |
As a Solution Architect, I need the platform to officially support and clearly document the architectural pattern of routing Read operations to a Secondary (replica) database and Update/Write operations to the Primary database. This allows enterprise clients to optimize performance for reporting and read-heavy business functions without degrading primary transactional performance. |
Preconditions |
The client environment is configured with a Primary database and at least one synchronized Secondary/Replica database. |
Trigger |
An architect or development team needs to scale application performance, isolate reporting workloads, or implement a CQRS (Command Query Responsibility Segregation) style pattern. |
Basic Flow |
1. Architect designs the application infrastructure to utilize a Read/Write split. 2. Developer accesses the official Jade Platform documentation for this architectural pattern. 3. Developer applies the documented configurations or code-level changes to route read queries to the secondary node. 4. The application successfully executes reports/reads against the secondary database while writes continue to hit the primary. |
Current Gap |
• Developers lack clarity and official guidance on how to implement this pattern within the Jade Platform ecosystem. • Absence of step-by-step documentation, best practices, or code/configuration examples. |
Expected Outcome |
• Publication of comprehensive, step-by-step developer documentation detailing how to configure and code for Read/Write database splitting. • Inclusion of architectural reference diagrams and code snippets. • Clear guidelines on handling edge cases (e.g., managing replication lag or connection string management). |
Priority |
Medium-High (Crucial for enterprise scalability and reporting performance) |
Acceptance Criteria |
• A developer can successfully configure a read-replica connection pattern using only the official documentation. • Documentation provides clear steps for separating read and write transactions at the application or connection level. • The development team can confidently validate that reporting queries are isolated to the secondary database. |
Guest
