Hi All, Message broker uses a relational database to store messages. More specifically these messages are stored in a table named as MB_CONTENT and MB_METADATA. What this means is regardless of the fact that data belongs to multiple queues, broker will utilize only one table-set for storage hence the performance broker (cluster) suffers when number of queues grows and/or cluster is in severe load.
Figure 1: Current high-level architecture of the related tables at wso2_mb. *Solution:* Allow users to have multiple table sets (for metadata and message content) and/or data sources configured in message broker that will make load of database is partitioned among multiple tables (or data sources) thus broker’s performance is not bounded by the performance of a single-table set. Figure 2: Suggested Solution (Number of table sets: 4) Please share your thoughts on this. Thanks, Udaka -- Udaka Ayas Manawadu *Intern,* WSO2, Inc. lean.enterprise.middleware Mobile: +94716836699 Email: [email protected] Linkedin: https://lk.linkedin.com/in/udakaayas
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
