[Architecture] WSO2 MB Proposed RDBMS Design

and delete tables. MB should not modify schema when joining to the cluster. There will be instances where MB users might not have privileges to create tables. *- Supporting several SQL implementations.* Since we are using simple SQL operations those will not become an issue. Thanks -- *Asitha

Re: [Architecture] WSO2 MB Proposed RDBMS Design

We are planning to insert message chunks as batch insert queries. On Sat, Jul 19, 2014 at 11:00 AM, Dhanuka Ranasinghe dhan...@wso2.com wrote: Are we going to insert whole message or as chunks On 18 Jul 2014 18:06, Asitha Nanayakkara asi...@wso2.com wrote: Hi, Following is the RDBMS

Re: [Architecture] WSO2 MB Proposed RDBMS Design

but again we will have to think about how gonna support fail over (probably have to change db schema). *Dhanuka Ranasinghe* Senior Software Engineer WSO2 Inc. ; http://wso2.com lean . enterprise . middleware phone : +94 715381915 On Mon, Jul 21, 2014 at 9:00 AM, Asitha Nanayakkara asi

Re: [Architecture] WSO2 MB Proposed RDBMS Design

with the respective message_id from Metadata table. In addition, to update reference count of messages an SQL trigger will be created. Is there any performance hit using triggers? On Thu, Jul 24, 2014 at 12:06 PM, Asitha Nanayakkara asi...@wso2.com wrote: With current design in memory message store

[Architecture] [Kernel][MB] Request to upgrade H2 DB version from 1.2.140 to 1.3.175 or above

4.3.0? [1] http://www.h2database.com/html/changelog.html Thanks -- *Asitha Nanayakkara* Software Engineer WSO2, Inc. http://wso2.com/ Mob: + 94 77 85 30 682 ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo

[Architecture] WSO2 MB Proposed RDBMS Design for Andes Context Store

has foreign key references to *exchanges* and *queue_info* tables. However if there is a performance hit in retrieving data we need to consider having redundant data in bindings table as well. -- *Asitha Nanayakkara* Software Engineer WSO2, Inc. http://wso2.com/ Mob: + 94 77 85 30 682

Re: [Architecture] WSO2 MB Proposed RDBMS Design

this design. Better we discuss upfront if so. It will bring changes to messageStore interface. Thanks On Thu, Jul 24, 2014 at 3:04 PM, Asitha Nanayakkara asi...@wso2.com wrote: With the addition of message expiration feature RDBMS design for Metadata in MB needs to be changed. Updated

Re: [Architecture] Batched content chunk reading for WSO2 MB through Disruptor

Hi Asanka, On Fri, Feb 13, 2015 at 1:46 PM, Asanka Abeyweera asank...@wso2.com wrote: HI Asitha, On Fri, Feb 13, 2015 at 1:30 PM, Asitha Nanayakkara asi...@wso2.com wrote: Hi Asanka, On Fri, Feb 13, 2015 at 1:07 PM, Asanka Abeyweera asank...@wso2.com wrote: On Fri, Feb 13, 2015

[Architecture] Batched content chunk reading for WSO2 MB through Disruptor

Hi Asanka, On Fri, Feb 13, 2015 at 1:07 PM, Asanka Abeyweera asank...@wso2.com wrote: On Fri, Feb 13, 2015 at 12:38 PM, Asitha Nanayakkara asi...@wso2.com wrote: Hi Asanka, On Fri, Feb 13, 2015 at 10:22 AM, Asanka Abeyweera asank...@wso2.com wrote: Hi Asitha , I don't think we need

Re: [Architecture] Batched content chunk reading for WSO2 MB through Disruptor

Hi Asanka, On Fri, Feb 13, 2015 at 2:32 PM, Asanka Abeyweera asank...@wso2.com wrote: Hi Asitha, On Fri, Feb 13, 2015 at 2:16 PM, Asitha Nanayakkara asi...@wso2.com wrote: Hi Asanka, On Fri, Feb 13, 2015 at 1:46 PM, Asanka Abeyweera asank...@wso2.com wrote: HI Asitha, On Fri, Feb

Re: [Architecture] [Dev]Enabling flow control in Message Broker based on channel size in Bytes

/listinfo/architecture -- *Asitha Nanayakkara* Software Engineer WSO2, Inc. http://wso2.com/ Mob: + 94 77 85 30 682 ___ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Re: [Architecture] Removing H2 In-memory Store Feature from MB 3.0

; > With Regards, > > On Fri, Sep 18, 2015 at 5:23 AM, Asitha Nanayakkara <asi...@wso2.com> > wrote: > >> Hi Yasassri, >> >> If I'm not mistaken, H2 In memory store is simply using the existing >> RDBMS message store implementations. The difference i

Re: [Architecture] Removing H2 In-memory Store Feature from MB 3.0

obile : +94715933168 <%2B94715933168>* > *Blogs : http://yasassriratnayake.blogspot.com > <http://yasassriratnayake.blogspot.com/>* > *http://wso2logs.blogspot.com <http://wso2logs.blogspot.com>* > -- *Asit

Re: [Architecture] [MB] Abstracting transport layer from core

_ >>> Architecture mailing list >>> Architecture@wso2.org >>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>> >>> >> >> >> -- >> *Kishanthan

Re: [Architecture] REST Services for MB 3.5.0 on C5

xO40gjTNhQgJnmz7_xZcue1FtQ14IlSdFI0jFIwnsF0/edit?usp=sharing > [2] - http://stackoverflow.com/a/8738518 > > > Regards, > Hemika > > Hemika Kodikara > Software Engineer > WSO2 Inc. > lean . enterprise . middleware > http://wso2.com > > Mobile : +9477762 > &

Re: [Architecture] RDBMS based coordinator election algorithm for MB

;>> >>>>>>>>>>>> The algorithm will use a polling mechanism to check the >>>>>>>>>>>> validity of the nodes. To make the election algorithm scalable, >>>>>>>>>>>> only the >>>>>>>&

Re: [Architecture] [MB4] JMS 2.0 Support

ired. >> >> Thank you, >> Maryam >> -- >> *Maryam Ziyad Mohamed* >> Software Engineer | WSO2 >> [image: http://wso2.com/signature] <http://wso2.com/signature> >> > > > > -- > *Maryam Ziyad Mohamed* > Software Engineer | WSO2 &

Re: [Architecture] Message routing rules for MB

http://wso2.com > *cell:* *+94 719363063* > *blog: **abeykoon.blogspot.com* <http://abeykoon.blogspot.com> > > ___ > Architecture mailing list > Architecture@wso2.org > https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture > -- *Asitha

Re: [Architecture] Message routing rules for MB

plemented in MB4? > If not shall we consider it to the roadmap? > > Thanks > > On Sat, Jun 23, 2018 at 7:00 AM Asitha Nanayakkara > wrote: > >> Header based routing can be done in AMQP. We can bind multiple queues >> with same routing key (that would be the queue name

[Architecture] [MB4] Restful Admin API's for Message Broker

criber DELETE /exchanges/{exchangeName}/destinations/{destinationName}/consumers/{consumerTag} When retrieving a set of exchanges, destinations or consumers we will be able to filter the result set by way of using query parameters. Regards, Asitha -- *Asitha Nanayakkara* <http://asitha.githu

Re: [Architecture] [MB4] Restful Admin API's for Message Broker

Adding Harshak, Sanjeewa and Malinthaa On Wed, Jan 10, 2018 at 5:37 PM, Asitha Nanayakkara <asi...@wso2.com> wrote: > Hi all, > > In the new message broker implementation we are implementing broker > semantics based on AMQP 0.9.1 specification. > > From an administrativ

Re: [Architecture] [MB4] Restful Admin API's for Message Broker

n, Asitha mentioned about default exchange; If > exchangeName is not provided can we use it as its default value? > > WDYT? > > Thanks! > > > On Wed, Jan 10, 2018 at 5:59 PM, Sanjeewa Malalgoda <sanje...@wso2.com> > wrote: > >> >> >> On Wed, Ja

Re: [Architecture] [MB4] Restful Admin API's for Message Broker

arate path for queues, outside /exchanges, we can have something like /queues. Used destinations to avoid the confusion with queues and topics. > > Thanks, > > On Wed, Jan 10, 2018 at 6:29 PM, Asitha Nanayakkara <asi...@wso2.com> > wrote: > >> Hi all, >> >>

Re: [Architecture] [MB4] Exposing messaging metrics

have a low footprint on the performance. > > WDYT? > [1]. http://isuru-perera.blogspot.com/2014/11/java-performance- > monitoring-libraries.html > [2]. https://github.com/dropwizard/metrics > > -- > Asanka Abeyweera > Associate Technical Lead > WSO2 Inc. > > Phone: +94 712

Re: [Architecture] [MB4] Exposing messaging metrics

echnical Lead >> WSO2 Inc. >> >> Phone: +94 712228648 <071%20222%208648> >> Blog: a5anka.github.io >> >> <https://wso2.com/signature> >> >> ___ >> Architecture mailing list >> Architectu

Re: [Architecture] [MB4] Restful Admin API's for Message Broker

tails - number messages etc >- Message details >- Permission details > - Binding details of a queue. Will be very useful for topic scenarios. > > > On Thu, Jan 11, 2018 at 12:41 AM, Eranda Rajapakshe <eran...@wso2.com> > wrote: > >> Hi Asitha, >>

Re: [Architecture] [MB4] Restful Admin API's for Message Broker

a API to purge a queue as well. > > Thanks > > On Fri, Jan 12, 2018 at 9:35 AM, Asitha Nanayakkara <asi...@wso2.com> > wrote: > >> Hi all, >> >> Taking all the concerns discussed in to account I did some updates on the >> design. >>

[Architecture] WSO2 Message Broker auth connector with WSO2 Identity Server

/MandatoryAccessController.java [3] https://github.com/ballerina-platform/ballerina-message-broker/blob/master/modules/broker-auth/src/main/java/io/ballerina/messaging/broker/auth/authorization/UserStore.java Regards, Asitha -- *Asitha Nanayakkara* <http://asitha.github.io/> Associate Technical Lead WSO2, Inc.

Re: [Architecture] WSO2 Message Broker auth connector with WSO2 Identity Server

an initial implementation. I believe we cannot install features like in Mb 3.x series here. > Yes you are correct. > > Thanks > > On Tue, Aug 14, 2018 at 9:54 AM Asitha Nanayakkara > wrote: > >> Hi all, >> >> Within Message Broker, there is an ext

Re: [Architecture] [Dev] [VOTE] Release WSO2 Integration Studio 7.1.0-RC1

tag to be voted upon: * >>> https://github.com/wso2/devstudio-tooling-ei/releases/tag/v7.1.0-rc1 >>> >>> Please download, test the features, and vote. >>> >>> [+] Stable - go ahead and release >>> >>> [-] Broken - do not release (explain