Hi Rohith, I believe , you have read and understand how the messaging engine works in wso2 message broker. Currently we are using apache cassandra for distributed brokering. With the proposal #13 , we are expecting to provide JDBC storage support for the wso2 message broker. With that ,we need to achieve all the functional requirements which we have up to now with cassandra. Then as the secondary step we can look in to the hybrid model for the storage.
As the first step , you can check out MB source code from [1] and have a look. [1] https://svn.wso2.org/repos/wso2/carbon/platform/branches/turing/dependencies/andes/0.13.0-wso2v11 Thanks Shammi On Tue, Mar 18, 2014 at 12:33 AM, Rohit Khapare <[email protected]>wrote: > Hello mentors, > > > > Here are my updates on proposal#13: > > In my understanding, the message broker nodes must be separate from the > Cassandra data nodes. So we can optimize the performance of the message > broker nodes by having an in-memory datastore such as Redis.io backed with > a distributed installation of MySQL for reliability purposes. > > > > However, I am struggling to gauge the feasibility of this solution. Please > guide me in the correct direction. > > > Regards, > Rohit Khapare > more about me at ➚[image: > https://encrypted-tbn3.gstatic.com/images?q=tbn:ANd9GcTBNQqheFsD9QI57uC_bMlpKbheSxBRzq-FDDzho_k-CvhejA6E]<http://www.linkedin.com/in/rohitkhapare/> > > *Wear a smile and have friends; wear a scowl and have wrinkles. - George > Eliot* > > > -- Best Regards, * Shammi Jayasinghe* Associate Tech Lead WSO2, Inc.; http://wso2.com, mobile: +94 71 4493085
<<inline: image001.jpg>>
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
