Re: [Architecture] Micro gateway profile for WSO2 EI - 6.3.0

[Malaka Gangananda]

Hi Milinda,

+1 for MicroESB.

Thanks,

On Thu, Jun 7, 2018 at 8:02 PM, Madhawa Gunasekara 
wrote:

> +1 for MicroESB
>
> On Thu, Jun 7, 2018 at 7:47 PM, Milinda Perera  wrote:
>
>> Hi Madhawa,
>>
>> What do you think about "MicroESB"?
>>
>> Thanks,
>> Milinda
>>
>> On Thu, Jun 7, 2018 at 10:37 AM, Madhawa Gunasekara 
>> wrote:
>>
>>> Hi All,
>>>
>>> We need to come up with a name for this profile.
>>>
>>> What's the name that we should put into this profile?
>>>
>>> lightweight ei or micro ei?
>>>
>>> Thanks,
>>> Madhawa
>>>
>>> On Wed, May 16, 2018 at 2:19 AM, Chamila De Alwis 
>>> wrote:
>>>
 Are we looking at optimizing memory usage also? At the moment, our
> recommendation is to use 1GB memory allocation at minimum. If we can 
> reduce
> this to a reasonable value, that would also be a good differentiation.
>

 This would be a really good goal to achieve. Less memory to request per
 container will be drastic differentiation from the existing EI. Most users,
 when mentioned "container-friendly" would expect memory usages to be in the
 MBs than in GBs.


 Regards,
 Chamila de Alwis
 Committer and PMC Member - Apache Stratos
 Associate Technical Lead | WSO2
 +94 77 220 7163
 Blog: https://medium.com/@chamilad



 On Tue, May 15, 2018 at 4:10 AM, Chanaka Fernando 
 wrote:

>
>
> On Tue, May 15, 2018 at 3:00 PM Isuru Udana  wrote:
>
>> Hi Chanaka,
>>
>> On Tue, May 15, 2018 at 2:55 PM Chanaka Fernando 
>> wrote:
>>
>>> Hi Madhawa,
>>>
>>> Could you elaborate more on the requirements for a micro ESB profile
>>> and what benefits we are trying to offer to the users with that? If we 
>>> are
>>> talking about building a profile which is 80% of the size of the 
>>> existing
>>> integration profile for running on containers, I don't see much value 
>>> out
>>> of this effort.
>>>
>> Our main focus is, reducing the startup time drastically.
>>
> That's a good point. If we can cut the startup time significantly,
> that would be really useful when running in containers. Are we looking at
> optimizing memory usage also? At the moment, our recommendation is to use
> 1GB memory allocation at minimum. If we can reduce this to a reasonable
> value, that would also be a good differentiation.
>
>>
>>> Thanks,
>>> Chanaka
>>>
>>> On Tue, May 8, 2018 at 1:29 AM Chamila De Alwis 
>>> wrote:
>>>
 Hi Madhawa,

 Aren't any DB operations involved in this profile?  Is the aim of
 removing Registry to strip down functionality?



 Regards,
 Chamila de Alwis
 Committer and PMC Member - Apache Stratos
 Associate Technical Lead | WSO2
 +94 77 220 7163
 Blog: https://medium.com/@chamilad



 On Thu, May 3, 2018 at 11:30 PM, Madhawa Gunasekara <
 madha...@wso2.com> wrote:

> Hi Isuru,
>
> Sure I will check on that.
>
> Thanks,
> Madhawa
>
> On Fri, May 4, 2018 at 8:42 AM, Isuru Udana 
> wrote:
>
>> Hi Madhawa,
>>
>> Subject is not correct. This is not about a micro gateway. This
>> is just a new ESB profile which is lightweight and a container 
>> friendly
>> one.
>>
>> Can you please check why we need registry for tasks. I believe it
>> is for coordination support. We might not need coordination support 
>> for
>> this profile.
>>
>> Thanks.
>>
>> On Thu, May 3, 2018 at 3:41 PM Nuwan Dias 
>> wrote:
>>
>>> Hi,
>>>
>>> Why is this being called Microgateway? This will cause huge
>>> confusion with the WSO2 API Manager's Gateway. Is this really a 
>>> Gateway
>>> profile or a stripped down version of the ESB?
>>>
>>> Thanks,
>>> NuwanD.
>>>
>>> On Thu, May 3, 2018 at 2:56 PM, Madhawa Gunasekara <
>>> madha...@wso2.com> wrote:
>>>
 Hi,

 I'm starting working on light weight ESB profile to work on
 containers. so basically we are trying to remove all the ui 
 components and
 the registry for that particular profile. but Tasks are depending 
 on the
 Registry. Therefore We need to find a way to provide tasks 
 functionality
 for this profile.

 @Integration team: Any thoughts and suggestions regarding this
 issue

 Thanks,
 Madhawa

 --
 *Madhawa Gunasekara*
 Senior Software Engineer
 WSO2 Inc.; 

Re: [Architecture] Micro gateway profile for WSO2 EI - 6.3.0

[Madhawa Gunasekara]

Hi Hasitha,

Yes, We do support inbound endpoints as well.

Thanks,
Madhawa

On Thu, Jun 7, 2018 at 7:54 PM, Hasitha Hiranya  wrote:

> Hi Madhawa,
>
> Does MicroESB profile support all the transports synapse+Axis2 supported?
> What about inbound transports? Any omits we did?
>
> Thanks
>
> On Thu, Jun 7, 2018 at 7:49 PM Milinda Perera  wrote:
>
>> Hi Madhawa,
>>
>> What do you think about "MicroESB"?
>>
>> Thanks,
>> Milinda
>>
>> On Thu, Jun 7, 2018 at 10:37 AM, Madhawa Gunasekara 
>> wrote:
>>
>>> Hi All,
>>>
>>> We need to come up with a name for this profile.
>>>
>>> What's the name that we should put into this profile?
>>>
>>> lightweight ei or micro ei?
>>>
>>> Thanks,
>>> Madhawa
>>>
>>> On Wed, May 16, 2018 at 2:19 AM, Chamila De Alwis 
>>> wrote:
>>>
 Are we looking at optimizing memory usage also? At the moment, our
> recommendation is to use 1GB memory allocation at minimum. If we can 
> reduce
> this to a reasonable value, that would also be a good differentiation.
>

 This would be a really good goal to achieve. Less memory to request per
 container will be drastic differentiation from the existing EI. Most users,
 when mentioned "container-friendly" would expect memory usages to be in the
 MBs than in GBs.


 Regards,
 Chamila de Alwis
 Committer and PMC Member - Apache Stratos
 Associate Technical Lead | WSO2
 +94 77 220 7163
 Blog: https://medium.com/@chamilad



 On Tue, May 15, 2018 at 4:10 AM, Chanaka Fernando 
 wrote:

>
>
> On Tue, May 15, 2018 at 3:00 PM Isuru Udana  wrote:
>
>> Hi Chanaka,
>>
>> On Tue, May 15, 2018 at 2:55 PM Chanaka Fernando 
>> wrote:
>>
>>> Hi Madhawa,
>>>
>>> Could you elaborate more on the requirements for a micro ESB profile
>>> and what benefits we are trying to offer to the users with that? If we 
>>> are
>>> talking about building a profile which is 80% of the size of the 
>>> existing
>>> integration profile for running on containers, I don't see much value 
>>> out
>>> of this effort.
>>>
>> Our main focus is, reducing the startup time drastically.
>>
> That's a good point. If we can cut the startup time significantly,
> that would be really useful when running in containers. Are we looking at
> optimizing memory usage also? At the moment, our recommendation is to use
> 1GB memory allocation at minimum. If we can reduce this to a reasonable
> value, that would also be a good differentiation.
>
>>
>>> Thanks,
>>> Chanaka
>>>
>>> On Tue, May 8, 2018 at 1:29 AM Chamila De Alwis 
>>> wrote:
>>>
 Hi Madhawa,

 Aren't any DB operations involved in this profile?  Is the aim of
 removing Registry to strip down functionality?



 Regards,
 Chamila de Alwis
 Committer and PMC Member - Apache Stratos
 Associate Technical Lead | WSO2
 +94 77 220 7163
 Blog: https://medium.com/@chamilad



 On Thu, May 3, 2018 at 11:30 PM, Madhawa Gunasekara <
 madha...@wso2.com> wrote:

> Hi Isuru,
>
> Sure I will check on that.
>
> Thanks,
> Madhawa
>
> On Fri, May 4, 2018 at 8:42 AM, Isuru Udana 
> wrote:
>
>> Hi Madhawa,
>>
>> Subject is not correct. This is not about a micro gateway. This
>> is just a new ESB profile which is lightweight and a container 
>> friendly
>> one.
>>
>> Can you please check why we need registry for tasks. I believe it
>> is for coordination support. We might not need coordination support 
>> for
>> this profile.
>>
>> Thanks.
>>
>> On Thu, May 3, 2018 at 3:41 PM Nuwan Dias 
>> wrote:
>>
>>> Hi,
>>>
>>> Why is this being called Microgateway? This will cause huge
>>> confusion with the WSO2 API Manager's Gateway. Is this really a 
>>> Gateway
>>> profile or a stripped down version of the ESB?
>>>
>>> Thanks,
>>> NuwanD.
>>>
>>> On Thu, May 3, 2018 at 2:56 PM, Madhawa Gunasekara <
>>> madha...@wso2.com> wrote:
>>>
 Hi,

 I'm starting working on light weight ESB profile to work on
 containers. so basically we are trying to remove all the ui 
 components and
 the registry for that particular profile. but Tasks are depending 
 on the
 Registry. Therefore We need to find a way to provide tasks 
 functionality
 for this profile.

 @Integration team: Any thoughts and suggestions regarding this
 issue

Re: [Architecture] Micro gateway profile for WSO2 EI - 6.3.0

[Madhawa Gunasekara]

+1 for MicroESB

On Thu, Jun 7, 2018 at 7:47 PM, Milinda Perera  wrote:

> Hi Madhawa,
>
> What do you think about "MicroESB"?
>
> Thanks,
> Milinda
>
> On Thu, Jun 7, 2018 at 10:37 AM, Madhawa Gunasekara 
> wrote:
>
>> Hi All,
>>
>> We need to come up with a name for this profile.
>>
>> What's the name that we should put into this profile?
>>
>> lightweight ei or micro ei?
>>
>> Thanks,
>> Madhawa
>>
>> On Wed, May 16, 2018 at 2:19 AM, Chamila De Alwis 
>> wrote:
>>
>>> Are we looking at optimizing memory usage also? At the moment, our
 recommendation is to use 1GB memory allocation at minimum. If we can reduce
 this to a reasonable value, that would also be a good differentiation.

>>>
>>> This would be a really good goal to achieve. Less memory to request per
>>> container will be drastic differentiation from the existing EI. Most users,
>>> when mentioned "container-friendly" would expect memory usages to be in the
>>> MBs than in GBs.
>>>
>>>
>>> Regards,
>>> Chamila de Alwis
>>> Committer and PMC Member - Apache Stratos
>>> Associate Technical Lead | WSO2
>>> +94 77 220 7163
>>> Blog: https://medium.com/@chamilad
>>>
>>>
>>>
>>> On Tue, May 15, 2018 at 4:10 AM, Chanaka Fernando 
>>> wrote:
>>>


 On Tue, May 15, 2018 at 3:00 PM Isuru Udana  wrote:

> Hi Chanaka,
>
> On Tue, May 15, 2018 at 2:55 PM Chanaka Fernando 
> wrote:
>
>> Hi Madhawa,
>>
>> Could you elaborate more on the requirements for a micro ESB profile
>> and what benefits we are trying to offer to the users with that? If we 
>> are
>> talking about building a profile which is 80% of the size of the existing
>> integration profile for running on containers, I don't see much value out
>> of this effort.
>>
> Our main focus is, reducing the startup time drastically.
>
 That's a good point. If we can cut the startup time significantly, that
 would be really useful when running in containers. Are we looking at
 optimizing memory usage also? At the moment, our recommendation is to use
 1GB memory allocation at minimum. If we can reduce this to a reasonable
 value, that would also be a good differentiation.

>
>> Thanks,
>> Chanaka
>>
>> On Tue, May 8, 2018 at 1:29 AM Chamila De Alwis 
>> wrote:
>>
>>> Hi Madhawa,
>>>
>>> Aren't any DB operations involved in this profile?  Is the aim of
>>> removing Registry to strip down functionality?
>>>
>>>
>>>
>>> Regards,
>>> Chamila de Alwis
>>> Committer and PMC Member - Apache Stratos
>>> Associate Technical Lead | WSO2
>>> +94 77 220 7163
>>> Blog: https://medium.com/@chamilad
>>>
>>>
>>>
>>> On Thu, May 3, 2018 at 11:30 PM, Madhawa Gunasekara <
>>> madha...@wso2.com> wrote:
>>>
 Hi Isuru,

 Sure I will check on that.

 Thanks,
 Madhawa

 On Fri, May 4, 2018 at 8:42 AM, Isuru Udana 
 wrote:

> Hi Madhawa,
>
> Subject is not correct. This is not about a micro gateway. This is
> just a new ESB profile which is lightweight and a container friendly 
> one.
>
> Can you please check why we need registry for tasks. I believe it
> is for coordination support. We might not need coordination support 
> for
> this profile.
>
> Thanks.
>
> On Thu, May 3, 2018 at 3:41 PM Nuwan Dias  wrote:
>
>> Hi,
>>
>> Why is this being called Microgateway? This will cause huge
>> confusion with the WSO2 API Manager's Gateway. Is this really a 
>> Gateway
>> profile or a stripped down version of the ESB?
>>
>> Thanks,
>> NuwanD.
>>
>> On Thu, May 3, 2018 at 2:56 PM, Madhawa Gunasekara <
>> madha...@wso2.com> wrote:
>>
>>> Hi,
>>>
>>> I'm starting working on light weight ESB profile to work on
>>> containers. so basically we are trying to remove all the ui 
>>> components and
>>> the registry for that particular profile. but Tasks are depending 
>>> on the
>>> Registry. Therefore We need to find a way to provide tasks 
>>> functionality
>>> for this profile.
>>>
>>> @Integration team: Any thoughts and suggestions regarding this
>>> issue
>>>
>>> Thanks,
>>> Madhawa
>>>
>>> --
>>> *Madhawa Gunasekara*
>>> Senior Software Engineer
>>> WSO2 Inc.; http://wso2.com
>>> lean.enterprise.middleware
>>>
>>> mobile: +94 719411002 <+94+719411002>
>>> blog: *http://madhawa-gunasekara.blogspot.com
>>> *
>>> linkedin: *http://lk.linkedin.com/in/mgunasekara
>>> 

Re: [Architecture] Micro gateway profile for WSO2 EI - 6.3.0

[Hasitha Hiranya]

Hi Madhawa,

Does MicroESB profile support all the transports synapse+Axis2 supported?
What about inbound transports? Any omits we did?

Thanks

On Thu, Jun 7, 2018 at 7:49 PM Milinda Perera  wrote:

> Hi Madhawa,
>
> What do you think about "MicroESB"?
>
> Thanks,
> Milinda
>
> On Thu, Jun 7, 2018 at 10:37 AM, Madhawa Gunasekara 
> wrote:
>
>> Hi All,
>>
>> We need to come up with a name for this profile.
>>
>> What's the name that we should put into this profile?
>>
>> lightweight ei or micro ei?
>>
>> Thanks,
>> Madhawa
>>
>> On Wed, May 16, 2018 at 2:19 AM, Chamila De Alwis 
>> wrote:
>>
>>> Are we looking at optimizing memory usage also? At the moment, our
 recommendation is to use 1GB memory allocation at minimum. If we can reduce
 this to a reasonable value, that would also be a good differentiation.

>>>
>>> This would be a really good goal to achieve. Less memory to request per
>>> container will be drastic differentiation from the existing EI. Most users,
>>> when mentioned "container-friendly" would expect memory usages to be in the
>>> MBs than in GBs.
>>>
>>>
>>> Regards,
>>> Chamila de Alwis
>>> Committer and PMC Member - Apache Stratos
>>> Associate Technical Lead | WSO2
>>> +94 77 220 7163
>>> Blog: https://medium.com/@chamilad
>>>
>>>
>>>
>>> On Tue, May 15, 2018 at 4:10 AM, Chanaka Fernando 
>>> wrote:
>>>


 On Tue, May 15, 2018 at 3:00 PM Isuru Udana  wrote:

> Hi Chanaka,
>
> On Tue, May 15, 2018 at 2:55 PM Chanaka Fernando 
> wrote:
>
>> Hi Madhawa,
>>
>> Could you elaborate more on the requirements for a micro ESB profile
>> and what benefits we are trying to offer to the users with that? If we 
>> are
>> talking about building a profile which is 80% of the size of the existing
>> integration profile for running on containers, I don't see much value out
>> of this effort.
>>
> Our main focus is, reducing the startup time drastically.
>
 That's a good point. If we can cut the startup time significantly, that
 would be really useful when running in containers. Are we looking at
 optimizing memory usage also? At the moment, our recommendation is to use
 1GB memory allocation at minimum. If we can reduce this to a reasonable
 value, that would also be a good differentiation.

>
>> Thanks,
>> Chanaka
>>
>> On Tue, May 8, 2018 at 1:29 AM Chamila De Alwis 
>> wrote:
>>
>>> Hi Madhawa,
>>>
>>> Aren't any DB operations involved in this profile?  Is the aim of
>>> removing Registry to strip down functionality?
>>>
>>>
>>>
>>> Regards,
>>> Chamila de Alwis
>>> Committer and PMC Member - Apache Stratos
>>> Associate Technical Lead | WSO2
>>> +94 77 220 7163
>>> Blog: https://medium.com/@chamilad
>>>
>>>
>>>
>>> On Thu, May 3, 2018 at 11:30 PM, Madhawa Gunasekara <
>>> madha...@wso2.com> wrote:
>>>
 Hi Isuru,

 Sure I will check on that.

 Thanks,
 Madhawa

 On Fri, May 4, 2018 at 8:42 AM, Isuru Udana 
 wrote:

> Hi Madhawa,
>
> Subject is not correct. This is not about a micro gateway. This is
> just a new ESB profile which is lightweight and a container friendly 
> one.
>
> Can you please check why we need registry for tasks. I believe it
> is for coordination support. We might not need coordination support 
> for
> this profile.
>
> Thanks.
>
> On Thu, May 3, 2018 at 3:41 PM Nuwan Dias  wrote:
>
>> Hi,
>>
>> Why is this being called Microgateway? This will cause huge
>> confusion with the WSO2 API Manager's Gateway. Is this really a 
>> Gateway
>> profile or a stripped down version of the ESB?
>>
>> Thanks,
>> NuwanD.
>>
>> On Thu, May 3, 2018 at 2:56 PM, Madhawa Gunasekara <
>> madha...@wso2.com> wrote:
>>
>>> Hi,
>>>
>>> I'm starting working on light weight ESB profile to work on
>>> containers. so basically we are trying to remove all the ui 
>>> components and
>>> the registry for that particular profile. but Tasks are depending 
>>> on the
>>> Registry. Therefore We need to find a way to provide tasks 
>>> functionality
>>> for this profile.
>>>
>>> @Integration team: Any thoughts and suggestions regarding this
>>> issue
>>>
>>> Thanks,
>>> Madhawa
>>>
>>> --
>>> *Madhawa Gunasekara*
>>> Senior Software Engineer
>>> WSO2 Inc.; http://wso2.com
>>> lean.enterprise.middleware
>>>
>>> mobile: +94 719411002 <+94+719411002>
>>> blog: *http://madhawa-gunasekara.blogspot.com

Re: [Architecture] Micro gateway profile for WSO2 EI - 6.3.0

[Milinda Perera]

Hi Madhawa,

What do you think about "MicroESB"?

Thanks,
Milinda

On Thu, Jun 7, 2018 at 10:37 AM, Madhawa Gunasekara 
wrote:

> Hi All,
>
> We need to come up with a name for this profile.
>
> What's the name that we should put into this profile?
>
> lightweight ei or micro ei?
>
> Thanks,
> Madhawa
>
> On Wed, May 16, 2018 at 2:19 AM, Chamila De Alwis 
> wrote:
>
>> Are we looking at optimizing memory usage also? At the moment, our
>>> recommendation is to use 1GB memory allocation at minimum. If we can reduce
>>> this to a reasonable value, that would also be a good differentiation.
>>>
>>
>> This would be a really good goal to achieve. Less memory to request per
>> container will be drastic differentiation from the existing EI. Most users,
>> when mentioned "container-friendly" would expect memory usages to be in the
>> MBs than in GBs.
>>
>>
>> Regards,
>> Chamila de Alwis
>> Committer and PMC Member - Apache Stratos
>> Associate Technical Lead | WSO2
>> +94 77 220 7163
>> Blog: https://medium.com/@chamilad
>>
>>
>>
>> On Tue, May 15, 2018 at 4:10 AM, Chanaka Fernando 
>> wrote:
>>
>>>
>>>
>>> On Tue, May 15, 2018 at 3:00 PM Isuru Udana  wrote:
>>>
 Hi Chanaka,

 On Tue, May 15, 2018 at 2:55 PM Chanaka Fernando 
 wrote:

> Hi Madhawa,
>
> Could you elaborate more on the requirements for a micro ESB profile
> and what benefits we are trying to offer to the users with that? If we are
> talking about building a profile which is 80% of the size of the existing
> integration profile for running on containers, I don't see much value out
> of this effort.
>
 Our main focus is, reducing the startup time drastically.

>>> That's a good point. If we can cut the startup time significantly, that
>>> would be really useful when running in containers. Are we looking at
>>> optimizing memory usage also? At the moment, our recommendation is to use
>>> 1GB memory allocation at minimum. If we can reduce this to a reasonable
>>> value, that would also be a good differentiation.
>>>

> Thanks,
> Chanaka
>
> On Tue, May 8, 2018 at 1:29 AM Chamila De Alwis 
> wrote:
>
>> Hi Madhawa,
>>
>> Aren't any DB operations involved in this profile?  Is the aim of
>> removing Registry to strip down functionality?
>>
>>
>>
>> Regards,
>> Chamila de Alwis
>> Committer and PMC Member - Apache Stratos
>> Associate Technical Lead | WSO2
>> +94 77 220 7163
>> Blog: https://medium.com/@chamilad
>>
>>
>>
>> On Thu, May 3, 2018 at 11:30 PM, Madhawa Gunasekara <
>> madha...@wso2.com> wrote:
>>
>>> Hi Isuru,
>>>
>>> Sure I will check on that.
>>>
>>> Thanks,
>>> Madhawa
>>>
>>> On Fri, May 4, 2018 at 8:42 AM, Isuru Udana  wrote:
>>>
 Hi Madhawa,

 Subject is not correct. This is not about a micro gateway. This is
 just a new ESB profile which is lightweight and a container friendly 
 one.

 Can you please check why we need registry for tasks. I believe it
 is for coordination support. We might not need coordination support for
 this profile.

 Thanks.

 On Thu, May 3, 2018 at 3:41 PM Nuwan Dias  wrote:

> Hi,
>
> Why is this being called Microgateway? This will cause huge
> confusion with the WSO2 API Manager's Gateway. Is this really a 
> Gateway
> profile or a stripped down version of the ESB?
>
> Thanks,
> NuwanD.
>
> On Thu, May 3, 2018 at 2:56 PM, Madhawa Gunasekara <
> madha...@wso2.com> wrote:
>
>> Hi,
>>
>> I'm starting working on light weight ESB profile to work on
>> containers. so basically we are trying to remove all the ui 
>> components and
>> the registry for that particular profile. but Tasks are depending on 
>> the
>> Registry. Therefore We need to find a way to provide tasks 
>> functionality
>> for this profile.
>>
>> @Integration team: Any thoughts and suggestions regarding this
>> issue
>>
>> Thanks,
>> Madhawa
>>
>> --
>> *Madhawa Gunasekara*
>> Senior Software Engineer
>> WSO2 Inc.; http://wso2.com
>> lean.enterprise.middleware
>>
>> mobile: +94 719411002 <+94+719411002>
>> blog: *http://madhawa-gunasekara.blogspot.com
>> *
>> linkedin: *http://lk.linkedin.com/in/mgunasekara
>> *
>>
>> ___
>> Architecture mailing list
>> Architecture@wso2.org
>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>
>>

Re: [Architecture] Micro gateway profile for WSO2 EI - 6.3.0

[Madhawa Gunasekara]

Hi All,

We need to come up with a name for this profile.

What's the name that we should put into this profile?

lightweight ei or micro ei?

Thanks,
Madhawa

On Wed, May 16, 2018 at 2:19 AM, Chamila De Alwis  wrote:

> Are we looking at optimizing memory usage also? At the moment, our
>> recommendation is to use 1GB memory allocation at minimum. If we can reduce
>> this to a reasonable value, that would also be a good differentiation.
>>
>
> This would be a really good goal to achieve. Less memory to request per
> container will be drastic differentiation from the existing EI. Most users,
> when mentioned "container-friendly" would expect memory usages to be in the
> MBs than in GBs.
>
>
> Regards,
> Chamila de Alwis
> Committer and PMC Member - Apache Stratos
> Associate Technical Lead | WSO2
> +94 77 220 7163
> Blog: https://medium.com/@chamilad
>
>
>
> On Tue, May 15, 2018 at 4:10 AM, Chanaka Fernando 
> wrote:
>
>>
>>
>> On Tue, May 15, 2018 at 3:00 PM Isuru Udana  wrote:
>>
>>> Hi Chanaka,
>>>
>>> On Tue, May 15, 2018 at 2:55 PM Chanaka Fernando 
>>> wrote:
>>>
 Hi Madhawa,

 Could you elaborate more on the requirements for a micro ESB profile
 and what benefits we are trying to offer to the users with that? If we are
 talking about building a profile which is 80% of the size of the existing
 integration profile for running on containers, I don't see much value out
 of this effort.

>>> Our main focus is, reducing the startup time drastically.
>>>
>> That's a good point. If we can cut the startup time significantly, that
>> would be really useful when running in containers. Are we looking at
>> optimizing memory usage also? At the moment, our recommendation is to use
>> 1GB memory allocation at minimum. If we can reduce this to a reasonable
>> value, that would also be a good differentiation.
>>
>>>
 Thanks,
 Chanaka

 On Tue, May 8, 2018 at 1:29 AM Chamila De Alwis 
 wrote:

> Hi Madhawa,
>
> Aren't any DB operations involved in this profile?  Is the aim of
> removing Registry to strip down functionality?
>
>
>
> Regards,
> Chamila de Alwis
> Committer and PMC Member - Apache Stratos
> Associate Technical Lead | WSO2
> +94 77 220 7163
> Blog: https://medium.com/@chamilad
>
>
>
> On Thu, May 3, 2018 at 11:30 PM, Madhawa Gunasekara  > wrote:
>
>> Hi Isuru,
>>
>> Sure I will check on that.
>>
>> Thanks,
>> Madhawa
>>
>> On Fri, May 4, 2018 at 8:42 AM, Isuru Udana  wrote:
>>
>>> Hi Madhawa,
>>>
>>> Subject is not correct. This is not about a micro gateway. This is
>>> just a new ESB profile which is lightweight and a container friendly 
>>> one.
>>>
>>> Can you please check why we need registry for tasks. I believe it is
>>> for coordination support. We might not need coordination support for 
>>> this
>>> profile.
>>>
>>> Thanks.
>>>
>>> On Thu, May 3, 2018 at 3:41 PM Nuwan Dias  wrote:
>>>
 Hi,

 Why is this being called Microgateway? This will cause huge
 confusion with the WSO2 API Manager's Gateway. Is this really a Gateway
 profile or a stripped down version of the ESB?

 Thanks,
 NuwanD.

 On Thu, May 3, 2018 at 2:56 PM, Madhawa Gunasekara <
 madha...@wso2.com> wrote:

> Hi,
>
> I'm starting working on light weight ESB profile to work on
> containers. so basically we are trying to remove all the ui 
> components and
> the registry for that particular profile. but Tasks are depending on 
> the
> Registry. Therefore We need to find a way to provide tasks 
> functionality
> for this profile.
>
> @Integration team: Any thoughts and suggestions regarding this
> issue
>
> Thanks,
> Madhawa
>
> --
> *Madhawa Gunasekara*
> Senior Software Engineer
> WSO2 Inc.; http://wso2.com
> lean.enterprise.middleware
>
> mobile: +94 719411002 <+94+719411002>
> blog: *http://madhawa-gunasekara.blogspot.com
> *
> linkedin: *http://lk.linkedin.com/in/mgunasekara
> *
>
> ___
> Architecture mailing list
> Architecture@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>
>


 --
 Nuwan Dias

 Software Architect - WSO2, Inc. http://wso2.com
 email : nuw...@wso2.com
 Phone : +94 777 775 729

>>>
>>>
>>> --
>>> *Isuru Udana*
>>> Senior Technical Lead
>>> WSO2 Inc.; http://wso2.com
>>> email: 

Re: [Architecture] Micro gateway profile for WSO2 EI - 6.3.0

[Chamila De Alwis]

>
> Are we looking at optimizing memory usage also? At the moment, our
> recommendation is to use 1GB memory allocation at minimum. If we can reduce
> this to a reasonable value, that would also be a good differentiation.
>

This would be a really good goal to achieve. Less memory to request per
container will be drastic differentiation from the existing EI. Most users,
when mentioned "container-friendly" would expect memory usages to be in the
MBs than in GBs.


Regards,
Chamila de Alwis
Committer and PMC Member - Apache Stratos
Associate Technical Lead | WSO2
+94 77 220 7163
Blog: https://medium.com/@chamilad



On Tue, May 15, 2018 at 4:10 AM, Chanaka Fernando  wrote:

>
>
> On Tue, May 15, 2018 at 3:00 PM Isuru Udana  wrote:
>
>> Hi Chanaka,
>>
>> On Tue, May 15, 2018 at 2:55 PM Chanaka Fernando 
>> wrote:
>>
>>> Hi Madhawa,
>>>
>>> Could you elaborate more on the requirements for a micro ESB profile and
>>> what benefits we are trying to offer to the users with that? If we are
>>> talking about building a profile which is 80% of the size of the existing
>>> integration profile for running on containers, I don't see much value out
>>> of this effort.
>>>
>> Our main focus is, reducing the startup time drastically.
>>
> That's a good point. If we can cut the startup time significantly, that
> would be really useful when running in containers. Are we looking at
> optimizing memory usage also? At the moment, our recommendation is to use
> 1GB memory allocation at minimum. If we can reduce this to a reasonable
> value, that would also be a good differentiation.
>
>>
>>> Thanks,
>>> Chanaka
>>>
>>> On Tue, May 8, 2018 at 1:29 AM Chamila De Alwis 
>>> wrote:
>>>
 Hi Madhawa,

 Aren't any DB operations involved in this profile?  Is the aim of
 removing Registry to strip down functionality?



 Regards,
 Chamila de Alwis
 Committer and PMC Member - Apache Stratos
 Associate Technical Lead | WSO2
 +94 77 220 7163
 Blog: https://medium.com/@chamilad



 On Thu, May 3, 2018 at 11:30 PM, Madhawa Gunasekara 
 wrote:

> Hi Isuru,
>
> Sure I will check on that.
>
> Thanks,
> Madhawa
>
> On Fri, May 4, 2018 at 8:42 AM, Isuru Udana  wrote:
>
>> Hi Madhawa,
>>
>> Subject is not correct. This is not about a micro gateway. This is
>> just a new ESB profile which is lightweight and a container friendly one.
>>
>> Can you please check why we need registry for tasks. I believe it is
>> for coordination support. We might not need coordination support for this
>> profile.
>>
>> Thanks.
>>
>> On Thu, May 3, 2018 at 3:41 PM Nuwan Dias  wrote:
>>
>>> Hi,
>>>
>>> Why is this being called Microgateway? This will cause huge
>>> confusion with the WSO2 API Manager's Gateway. Is this really a Gateway
>>> profile or a stripped down version of the ESB?
>>>
>>> Thanks,
>>> NuwanD.
>>>
>>> On Thu, May 3, 2018 at 2:56 PM, Madhawa Gunasekara <
>>> madha...@wso2.com> wrote:
>>>
 Hi,

 I'm starting working on light weight ESB profile to work on
 containers. so basically we are trying to remove all the ui components 
 and
 the registry for that particular profile. but Tasks are depending on 
 the
 Registry. Therefore We need to find a way to provide tasks 
 functionality
 for this profile.

 @Integration team: Any thoughts and suggestions regarding this issue

 Thanks,
 Madhawa

 --
 *Madhawa Gunasekara*
 Senior Software Engineer
 WSO2 Inc.; http://wso2.com
 lean.enterprise.middleware

 mobile: +94 719411002 <+94+719411002>
 blog: *http://madhawa-gunasekara.blogspot.com
 *
 linkedin: *http://lk.linkedin.com/in/mgunasekara
 *

 ___
 Architecture mailing list
 Architecture@wso2.org
 https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture


>>>
>>>
>>> --
>>> Nuwan Dias
>>>
>>> Software Architect - WSO2, Inc. http://wso2.com
>>> email : nuw...@wso2.com
>>> Phone : +94 777 775 729
>>>
>>
>>
>> --
>> *Isuru Udana*
>> Senior Technical Lead
>> WSO2 Inc.; http://wso2.com
>> email: isu...@wso2.com cell: +94 77 3791887
>> blog: http://mytecheye.blogspot.com/
>>
>> ___
>> Architecture mailing list
>> Architecture@wso2.org
>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>
>>

Re: [Architecture] Micro gateway profile for WSO2 EI - 6.3.0

[Chanaka Fernando]

On Tue, May 15, 2018 at 3:00 PM Isuru Udana  wrote:

> Hi Chanaka,
>
> On Tue, May 15, 2018 at 2:55 PM Chanaka Fernando 
> wrote:
>
>> Hi Madhawa,
>>
>> Could you elaborate more on the requirements for a micro ESB profile and
>> what benefits we are trying to offer to the users with that? If we are
>> talking about building a profile which is 80% of the size of the existing
>> integration profile for running on containers, I don't see much value out
>> of this effort.
>>
> Our main focus is, reducing the startup time drastically.
>
That's a good point. If we can cut the startup time significantly, that
would be really useful when running in containers. Are we looking at
optimizing memory usage also? At the moment, our recommendation is to use
1GB memory allocation at minimum. If we can reduce this to a reasonable
value, that would also be a good differentiation.

>
>> Thanks,
>> Chanaka
>>
>> On Tue, May 8, 2018 at 1:29 AM Chamila De Alwis 
>> wrote:
>>
>>> Hi Madhawa,
>>>
>>> Aren't any DB operations involved in this profile?  Is the aim of
>>> removing Registry to strip down functionality?
>>>
>>>
>>>
>>> Regards,
>>> Chamila de Alwis
>>> Committer and PMC Member - Apache Stratos
>>> Associate Technical Lead | WSO2
>>> +94 77 220 7163
>>> Blog: https://medium.com/@chamilad
>>>
>>>
>>>
>>> On Thu, May 3, 2018 at 11:30 PM, Madhawa Gunasekara 
>>> wrote:
>>>
 Hi Isuru,

 Sure I will check on that.

 Thanks,
 Madhawa

 On Fri, May 4, 2018 at 8:42 AM, Isuru Udana  wrote:

> Hi Madhawa,
>
> Subject is not correct. This is not about a micro gateway. This is
> just a new ESB profile which is lightweight and a container friendly one.
>
> Can you please check why we need registry for tasks. I believe it is
> for coordination support. We might not need coordination support for this
> profile.
>
> Thanks.
>
> On Thu, May 3, 2018 at 3:41 PM Nuwan Dias  wrote:
>
>> Hi,
>>
>> Why is this being called Microgateway? This will cause huge confusion
>> with the WSO2 API Manager's Gateway. Is this really a Gateway profile or 
>> a
>> stripped down version of the ESB?
>>
>> Thanks,
>> NuwanD.
>>
>> On Thu, May 3, 2018 at 2:56 PM, Madhawa Gunasekara > > wrote:
>>
>>> Hi,
>>>
>>> I'm starting working on light weight ESB profile to work on
>>> containers. so basically we are trying to remove all the ui components 
>>> and
>>> the registry for that particular profile. but Tasks are depending on the
>>> Registry. Therefore We need to find a way to provide tasks functionality
>>> for this profile.
>>>
>>> @Integration team: Any thoughts and suggestions regarding this issue
>>>
>>> Thanks,
>>> Madhawa
>>>
>>> --
>>> *Madhawa Gunasekara*
>>> Senior Software Engineer
>>> WSO2 Inc.; http://wso2.com
>>> lean.enterprise.middleware
>>>
>>> mobile: +94 719411002 <+94+719411002>
>>> blog: *http://madhawa-gunasekara.blogspot.com
>>> *
>>> linkedin: *http://lk.linkedin.com/in/mgunasekara
>>> *
>>>
>>> ___
>>> Architecture mailing list
>>> Architecture@wso2.org
>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>>
>>>
>>
>>
>> --
>> Nuwan Dias
>>
>> Software Architect - WSO2, Inc. http://wso2.com
>> email : nuw...@wso2.com
>> Phone : +94 777 775 729
>>
>
>
> --
> *Isuru Udana*
> Senior Technical Lead
> WSO2 Inc.; http://wso2.com
> email: isu...@wso2.com cell: +94 77 3791887
> blog: http://mytecheye.blogspot.com/
>
> ___
> Architecture mailing list
> Architecture@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>
>


 --
 *Madhawa Gunasekara*
 Senior Software Engineer
 WSO2 Inc.; http://wso2.com
 lean.enterprise.middleware

 mobile: +94 719411002 <+94+719411002>
 blog: *http://madhawa-gunasekara.blogspot.com
 *
 linkedin: *http://lk.linkedin.com/in/mgunasekara
 *

 ___
 Architecture mailing list
 Architecture@wso2.org
 https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture


>>> ___
>>> Architecture mailing list
>>> Architecture@wso2.org
>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>>
>>
>>
>> --
>> Thank you and Best Regards,
>> Chanaka Fernando
>> Associate Director/ Solutions Architect
>> m: 

Re: [Architecture] Micro gateway profile for WSO2 EI - 6.3.0

[Isuru Udana]

Hi Chanaka,

On Tue, May 15, 2018 at 2:55 PM Chanaka Fernando  wrote:

> Hi Madhawa,
>
> Could you elaborate more on the requirements for a micro ESB profile and
> what benefits we are trying to offer to the users with that? If we are
> talking about building a profile which is 80% of the size of the existing
> integration profile for running on containers, I don't see much value out
> of this effort.
>
Our main focus is, reducing the startup time drastically.

>
> Thanks,
> Chanaka
>
> On Tue, May 8, 2018 at 1:29 AM Chamila De Alwis  wrote:
>
>> Hi Madhawa,
>>
>> Aren't any DB operations involved in this profile?  Is the aim of
>> removing Registry to strip down functionality?
>>
>>
>>
>> Regards,
>> Chamila de Alwis
>> Committer and PMC Member - Apache Stratos
>> Associate Technical Lead | WSO2
>> +94 77 220 7163
>> Blog: https://medium.com/@chamilad
>>
>>
>>
>> On Thu, May 3, 2018 at 11:30 PM, Madhawa Gunasekara 
>> wrote:
>>
>>> Hi Isuru,
>>>
>>> Sure I will check on that.
>>>
>>> Thanks,
>>> Madhawa
>>>
>>> On Fri, May 4, 2018 at 8:42 AM, Isuru Udana  wrote:
>>>
 Hi Madhawa,

 Subject is not correct. This is not about a micro gateway. This is just
 a new ESB profile which is lightweight and a container friendly one.

 Can you please check why we need registry for tasks. I believe it is
 for coordination support. We might not need coordination support for this
 profile.

 Thanks.

 On Thu, May 3, 2018 at 3:41 PM Nuwan Dias  wrote:

> Hi,
>
> Why is this being called Microgateway? This will cause huge confusion
> with the WSO2 API Manager's Gateway. Is this really a Gateway profile or a
> stripped down version of the ESB?
>
> Thanks,
> NuwanD.
>
> On Thu, May 3, 2018 at 2:56 PM, Madhawa Gunasekara 
> wrote:
>
>> Hi,
>>
>> I'm starting working on light weight ESB profile to work on
>> containers. so basically we are trying to remove all the ui components 
>> and
>> the registry for that particular profile. but Tasks are depending on the
>> Registry. Therefore We need to find a way to provide tasks functionality
>> for this profile.
>>
>> @Integration team: Any thoughts and suggestions regarding this issue
>>
>> Thanks,
>> Madhawa
>>
>> --
>> *Madhawa Gunasekara*
>> Senior Software Engineer
>> WSO2 Inc.; http://wso2.com
>> lean.enterprise.middleware
>>
>> mobile: +94 719411002 <+94+719411002>
>> blog: *http://madhawa-gunasekara.blogspot.com
>> *
>> linkedin: *http://lk.linkedin.com/in/mgunasekara
>> *
>>
>> ___
>> Architecture mailing list
>> Architecture@wso2.org
>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>
>>
>
>
> --
> Nuwan Dias
>
> Software Architect - WSO2, Inc. http://wso2.com
> email : nuw...@wso2.com
> Phone : +94 777 775 729
>


 --
 *Isuru Udana*
 Senior Technical Lead
 WSO2 Inc.; http://wso2.com
 email: isu...@wso2.com cell: +94 77 3791887
 blog: http://mytecheye.blogspot.com/

 ___
 Architecture mailing list
 Architecture@wso2.org
 https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture


>>>
>>>
>>> --
>>> *Madhawa Gunasekara*
>>> Senior Software Engineer
>>> WSO2 Inc.; http://wso2.com
>>> lean.enterprise.middleware
>>>
>>> mobile: +94 719411002 <+94+719411002>
>>> blog: *http://madhawa-gunasekara.blogspot.com
>>> *
>>> linkedin: *http://lk.linkedin.com/in/mgunasekara
>>> *
>>>
>>> ___
>>> Architecture mailing list
>>> Architecture@wso2.org
>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>>
>>>
>> ___
>> Architecture mailing list
>> Architecture@wso2.org
>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>
>
>
> --
> Thank you and Best Regards,
> Chanaka Fernando
> Associate Director/ Solutions Architect
> m: +94 773337238
> twitter: @chanakaudaya
> linkedIn: https://www.linkedin.com/in/chanaka-fernando-5b0a2019/
> https://wso2.com 
>
>
>
>
>
>
> ___
> Architecture mailing list
> Architecture@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>


-- 
*Isuru Udana*
Senior Technical Lead
WSO2 Inc.; http://wso2.com
email: isu...@wso2.com cell: +94 77 3791887
blog: http://mytecheye.blogspot.com/
___
Architecture mailing list
Architecture@wso2.org

Re: [Architecture] Micro gateway profile for WSO2 EI - 6.3.0

[Chanaka Fernando]

Hi Madhawa,

Could you elaborate more on the requirements for a micro ESB profile and
what benefits we are trying to offer to the users with that? If we are
talking about building a profile which is 80% of the size of the existing
integration profile for running on containers, I don't see much value out
of this effort.

Thanks,
Chanaka

On Tue, May 8, 2018 at 1:29 AM Chamila De Alwis  wrote:

> Hi Madhawa,
>
> Aren't any DB operations involved in this profile?  Is the aim of removing
> Registry to strip down functionality?
>
>
>
> Regards,
> Chamila de Alwis
> Committer and PMC Member - Apache Stratos
> Associate Technical Lead | WSO2
> +94 77 220 7163
> Blog: https://medium.com/@chamilad
>
>
>
> On Thu, May 3, 2018 at 11:30 PM, Madhawa Gunasekara 
> wrote:
>
>> Hi Isuru,
>>
>> Sure I will check on that.
>>
>> Thanks,
>> Madhawa
>>
>> On Fri, May 4, 2018 at 8:42 AM, Isuru Udana  wrote:
>>
>>> Hi Madhawa,
>>>
>>> Subject is not correct. This is not about a micro gateway. This is just
>>> a new ESB profile which is lightweight and a container friendly one.
>>>
>>> Can you please check why we need registry for tasks. I believe it is for
>>> coordination support. We might not need coordination support for this
>>> profile.
>>>
>>> Thanks.
>>>
>>> On Thu, May 3, 2018 at 3:41 PM Nuwan Dias  wrote:
>>>
 Hi,

 Why is this being called Microgateway? This will cause huge confusion
 with the WSO2 API Manager's Gateway. Is this really a Gateway profile or a
 stripped down version of the ESB?

 Thanks,
 NuwanD.

 On Thu, May 3, 2018 at 2:56 PM, Madhawa Gunasekara 
 wrote:

> Hi,
>
> I'm starting working on light weight ESB profile to work on
> containers. so basically we are trying to remove all the ui components and
> the registry for that particular profile. but Tasks are depending on the
> Registry. Therefore We need to find a way to provide tasks functionality
> for this profile.
>
> @Integration team: Any thoughts and suggestions regarding this issue
>
> Thanks,
> Madhawa
>
> --
> *Madhawa Gunasekara*
> Senior Software Engineer
> WSO2 Inc.; http://wso2.com
> lean.enterprise.middleware
>
> mobile: +94 719411002 <+94+719411002>
> blog: *http://madhawa-gunasekara.blogspot.com
> *
> linkedin: *http://lk.linkedin.com/in/mgunasekara
> *
>
> ___
> Architecture mailing list
> Architecture@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>
>


 --
 Nuwan Dias

 Software Architect - WSO2, Inc. http://wso2.com
 email : nuw...@wso2.com
 Phone : +94 777 775 729

>>>
>>>
>>> --
>>> *Isuru Udana*
>>> Senior Technical Lead
>>> WSO2 Inc.; http://wso2.com
>>> email: isu...@wso2.com cell: +94 77 3791887
>>> blog: http://mytecheye.blogspot.com/
>>>
>>> ___
>>> Architecture mailing list
>>> Architecture@wso2.org
>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>>
>>>
>>
>>
>> --
>> *Madhawa Gunasekara*
>> Senior Software Engineer
>> WSO2 Inc.; http://wso2.com
>> lean.enterprise.middleware
>>
>> mobile: +94 719411002 <+94+719411002>
>> blog: *http://madhawa-gunasekara.blogspot.com
>> *
>> linkedin: *http://lk.linkedin.com/in/mgunasekara
>> *
>>
>> ___
>> Architecture mailing list
>> Architecture@wso2.org
>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>
>>
> ___
> Architecture mailing list
> Architecture@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>


-- 
Thank you and Best Regards,
Chanaka Fernando
Associate Director/ Solutions Architect
m: +94 773337238
twitter: @chanakaudaya
linkedIn: https://www.linkedin.com/in/chanaka-fernando-5b0a2019/
https://wso2.com 
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Re: [Architecture] Micro gateway profile for WSO2 EI - 6.3.0

[Chamila De Alwis]

Hi Madhawa,

Aren't any DB operations involved in this profile?  Is the aim of removing
Registry to strip down functionality?



Regards,
Chamila de Alwis
Committer and PMC Member - Apache Stratos
Associate Technical Lead | WSO2
+94 77 220 7163
Blog: https://medium.com/@chamilad



On Thu, May 3, 2018 at 11:30 PM, Madhawa Gunasekara 
wrote:

> Hi Isuru,
>
> Sure I will check on that.
>
> Thanks,
> Madhawa
>
> On Fri, May 4, 2018 at 8:42 AM, Isuru Udana  wrote:
>
>> Hi Madhawa,
>>
>> Subject is not correct. This is not about a micro gateway. This is just a
>> new ESB profile which is lightweight and a container friendly one.
>>
>> Can you please check why we need registry for tasks. I believe it is for
>> coordination support. We might not need coordination support for this
>> profile.
>>
>> Thanks.
>>
>> On Thu, May 3, 2018 at 3:41 PM Nuwan Dias  wrote:
>>
>>> Hi,
>>>
>>> Why is this being called Microgateway? This will cause huge confusion
>>> with the WSO2 API Manager's Gateway. Is this really a Gateway profile or a
>>> stripped down version of the ESB?
>>>
>>> Thanks,
>>> NuwanD.
>>>
>>> On Thu, May 3, 2018 at 2:56 PM, Madhawa Gunasekara 
>>> wrote:
>>>
 Hi,

 I'm starting working on light weight ESB profile to work on containers.
 so basically we are trying to remove all the ui components and the registry
 for that particular profile. but Tasks are depending on the Registry.
 Therefore We need to find a way to provide tasks functionality for this
 profile.

 @Integration team: Any thoughts and suggestions regarding this issue

 Thanks,
 Madhawa

 --
 *Madhawa Gunasekara*
 Senior Software Engineer
 WSO2 Inc.; http://wso2.com
 lean.enterprise.middleware

 mobile: +94 719411002 <+94+719411002>
 blog: *http://madhawa-gunasekara.blogspot.com
 *
 linkedin: *http://lk.linkedin.com/in/mgunasekara
 *

 ___
 Architecture mailing list
 Architecture@wso2.org
 https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture


>>>
>>>
>>> --
>>> Nuwan Dias
>>>
>>> Software Architect - WSO2, Inc. http://wso2.com
>>> email : nuw...@wso2.com
>>> Phone : +94 777 775 729
>>>
>>
>>
>> --
>> *Isuru Udana*
>> Senior Technical Lead
>> WSO2 Inc.; http://wso2.com
>> email: isu...@wso2.com cell: +94 77 3791887
>> blog: http://mytecheye.blogspot.com/
>>
>> ___
>> Architecture mailing list
>> Architecture@wso2.org
>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>
>>
>
>
> --
> *Madhawa Gunasekara*
> Senior Software Engineer
> WSO2 Inc.; http://wso2.com
> lean.enterprise.middleware
>
> mobile: +94 719411002 <+94+719411002>
> blog: *http://madhawa-gunasekara.blogspot.com
> *
> linkedin: *http://lk.linkedin.com/in/mgunasekara
> *
>
> ___
> Architecture mailing list
> Architecture@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>
>
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Re: [Architecture] Micro gateway profile for WSO2 EI - 6.3.0

[Isuru Udana]

Hi Madhawa,

Subject is not correct. This is not about a micro gateway. This is just a
new ESB profile which is lightweight and a container friendly one.

Can you please check why we need registry for tasks. I believe it is for
coordination support. We might not need coordination support for this
profile.

Thanks.

On Thu, May 3, 2018 at 3:41 PM Nuwan Dias  wrote:

> Hi,
>
> Why is this being called Microgateway? This will cause huge confusion with
> the WSO2 API Manager's Gateway. Is this really a Gateway profile or a
> stripped down version of the ESB?
>
> Thanks,
> NuwanD.
>
> On Thu, May 3, 2018 at 2:56 PM, Madhawa Gunasekara 
> wrote:
>
>> Hi,
>>
>> I'm starting working on light weight ESB profile to work on containers.
>> so basically we are trying to remove all the ui components and the registry
>> for that particular profile. but Tasks are depending on the Registry.
>> Therefore We need to find a way to provide tasks functionality for this
>> profile.
>>
>> @Integration team: Any thoughts and suggestions regarding this issue
>>
>> Thanks,
>> Madhawa
>>
>> --
>> *Madhawa Gunasekara*
>> Senior Software Engineer
>> WSO2 Inc.; http://wso2.com
>> lean.enterprise.middleware
>>
>> mobile: +94 719411002 <+94+719411002>
>> blog: *http://madhawa-gunasekara.blogspot.com
>> *
>> linkedin: *http://lk.linkedin.com/in/mgunasekara
>> *
>>
>> ___
>> Architecture mailing list
>> Architecture@wso2.org
>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>
>>
>
>
> --
> Nuwan Dias
>
> Software Architect - WSO2, Inc. http://wso2.com
> email : nuw...@wso2.com
> Phone : +94 777 775 729
>


-- 
*Isuru Udana*
Senior Technical Lead
WSO2 Inc.; http://wso2.com
email: isu...@wso2.com cell: +94 77 3791887
blog: http://mytecheye.blogspot.com/
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Re: [Architecture] Micro gateway profile for WSO2 EI - 6.3.0

[Nuwan Dias]

Hi,

Why is this being called Microgateway? This will cause huge confusion with
the WSO2 API Manager's Gateway. Is this really a Gateway profile or a
stripped down version of the ESB?

Thanks,
NuwanD.

On Thu, May 3, 2018 at 2:56 PM, Madhawa Gunasekara 
wrote:

> Hi,
>
> I'm starting working on light weight ESB profile to work on containers. so
> basically we are trying to remove all the ui components and the registry
> for that particular profile. but Tasks are depending on the Registry.
> Therefore We need to find a way to provide tasks functionality for this
> profile.
>
> @Integration team: Any thoughts and suggestions regarding this issue
>
> Thanks,
> Madhawa
>
> --
> *Madhawa Gunasekara*
> Senior Software Engineer
> WSO2 Inc.; http://wso2.com
> lean.enterprise.middleware
>
> mobile: +94 719411002 <+94+719411002>
> blog: *http://madhawa-gunasekara.blogspot.com
> *
> linkedin: *http://lk.linkedin.com/in/mgunasekara
> *
>
> ___
> Architecture mailing list
> Architecture@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>
>


-- 
Nuwan Dias

Software Architect - WSO2, Inc. http://wso2.com
email : nuw...@wso2.com
Phone : +94 777 775 729
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture