You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@synapse.apache.org by Madhawa Kasun Gunasekara <ma...@gmail.com> on 2020/01/07 18:10:32 UTC
Re: Positioning Synapse as an Integration Framework
+1,
Moving forward for the container friendly integration framework is a great
idea. How about considering for version 4.x.x. release. I can help too.
Thanks,
Madhawa
On Thu, Dec 12, 2019 at 2:38 AM Isuru Udana <is...@apache.org> wrote:
> Hi All,
>
> It has been 12 years since Synapse was founded (2007-12-19). As we all
> know in the last few years we did not have a good run. The activity of the
> project has significantly gone down and there is not much of a contribution
> from the majority of the committers.
>
> Also, ESB architectural style is no longer the preferred style for doing
> the integration. The world has been moved towards container friendly
> products, microservices, and cloud-native technologies. However, the
> integration problem solved by the ESB architecture still exists and handled
> by different entities.
>
> Even though Synapse is an ESB, it has most of the qualities (ex: faster
> startup time, low resource consumption, etc.) that are important for
> containers and microservices integrations. So with a little effort, we
> could make Synapse a container friendly product that suits any
> architectural style for doing the integration.
>
> So, should we consider positioning Synapse as an 'Integration Framework'
> or an 'Integration Product' that serves all architectural styles?
> Will that help us reactivate the project?
>
> Please share your thoughts.
>
> Thank you.
>
>
>
> ---------- Forwarded message ---------
> From: Isuru Udana <is...@gmail.com>
> Date: Thu, Dec 12, 2019 at 7:03 AM
> Subject: Re: Positioning Synapse as an Integration Framework
> To: <pr...@synapse.apache.org>
>
>
> I will open this discussion to the community to reach a wide audience.
>
> On Wed, Dec 11, 2019 at 5:20 AM Vanjikumaran Sivajothy <
> vanjikumaran@gmail.com> wrote:
>
>> I am not too sure about adopting the very abstract term Integration
>> Framework; However, I can assure that moving towards container-native is a
>> logical move.
>> I can help on this to produce an initial set of artifacts.
>>
>>
>>
>> On Mon, Dec 2, 2019 at 4:23 PM Isuru Udana <is...@gmail.com> wrote:
>>
>> > Hi PMC,
>> >
>> > It has been 12 years since Synapse was founded (2007-12-19). As we all
>> know
>> > in the last few years we did not have a good run. The activity of the
>> > project has significantly gone down and there is not much of a
>> contribution
>> > from the majority of the committers/PMC members.
>> >
>> > Also, ESB architectural style is no longer the preferred style for doing
>> > the integration. The world has been moved towards container friendly
>> > products, microservices, and cloud-native technologies. However, the
>> > integration problem solved by the ESB architecture still exists and
>> handled
>> > by different entities.
>> >
>> > Even though Synapse is an ESB, it has most of the qualities (ex: faster
>> > startup time, low resource consumption, etc.) that are important for
>> > containers and microservices integrations. So with a little effort, we
>> > could make Synapse a container friendly product that suits any
>> > architectural style for doing the integration.
>> >
>> > So, should we consider positioning Synapse as an 'Integration
>> Framework' or
>> > an 'Integration Product' that serves all architectural styles?
>> > Will that help us reactivate the project?
>> >
>> >
>> > --
>> > *Isuru Udana*
>> >
>> >
>> >
>> > *email: isudana@gmail.com <is...@gmail.com> blog:
>> > http://mytecheye.blogspot.com/ <http://mytecheye.blogspot.com/>*
>> >
>>
>>
>> --
>> Best Regards,
>> Vanji
>>
>
>
> --
> *Isuru Udana*
> Senior Technical Lead
>
>
>
>
> *; WSO2 Inc.; http://wso2.com <http://wso2.com>email: isudana@gmail.com
> <is...@gmail.com> blog: http://mytecheye.blogspot.com/
> <http://mytecheye.blogspot.com/>*
>
>
>
>
Re: Positioning Synapse as an Integration Framework
Posted by Madhawa Kasun Gunasekara <ma...@gmail.com>.
Hi,
We came up with the below list.
Tasks
-
Reduce memory footprint
-
Create docker, Kubernetes artifacts [
https://issues.apache.org/jira/projects/SYNAPSE/issues/SYNAPSE-1111]
-
Integrate travis/jenkins for the pull requests - Isuru
-
JDK11 support (openjdk) [
https://issues.apache.org/jira/projects/SYNAPSE/issues/SYNAPSE-1112]
-
Unit testing framework
-
Netty transport
Thanks,
Madhawa
On Thu, Feb 13, 2020 at 4:26 PM Isuru Udana <is...@gmail.com> wrote:
>
>
> On Thu, Feb 13, 2020 at 8:53 PM Madhawa Kasun Gunasekara <
> madhawa30@gmail.com> wrote:
>
>> Hi All,
>>
>> Shall we start working on this? I believe there are so many things to
>> improve. so let's start listing them. after that, we can prioritize items
>> and create Jira tickets.
>>
>> +1. I will first work on integrating a build system (Travis or Jenkins)
> for Pull Requests, that will make PR merging easier.
>
> Thanks.
>
>
>> Thanks,
>> Madhawa
>>
>>
>> On Tue, Jan 7, 2020 at 7:10 PM Madhawa Kasun Gunasekara <
>> madhawa30@gmail.com> wrote:
>>
>>> +1,
>>> Moving forward for the container friendly integration framework is a
>>> great idea. How about considering for version 4.x.x. release. I can help
>>> too.
>>>
>>> Thanks,
>>> Madhawa
>>>
>>>
>>> On Thu, Dec 12, 2019 at 2:38 AM Isuru Udana <is...@apache.org> wrote:
>>>
>>>> Hi All,
>>>>
>>>> It has been 12 years since Synapse was founded (2007-12-19). As we all
>>>> know in the last few years we did not have a good run. The activity of the
>>>> project has significantly gone down and there is not much of a contribution
>>>> from the majority of the committers.
>>>>
>>>> Also, ESB architectural style is no longer the preferred style for
>>>> doing the integration. The world has been moved towards container friendly
>>>> products, microservices, and cloud-native technologies. However, the
>>>> integration problem solved by the ESB architecture still exists and handled
>>>> by different entities.
>>>>
>>>> Even though Synapse is an ESB, it has most of the qualities (ex: faster
>>>> startup time, low resource consumption, etc.) that are important for
>>>> containers and microservices integrations. So with a little effort, we
>>>> could make Synapse a container friendly product that suits any
>>>> architectural style for doing the integration.
>>>>
>>>> So, should we consider positioning Synapse as an 'Integration
>>>> Framework' or an 'Integration Product' that serves all architectural styles?
>>>> Will that help us reactivate the project?
>>>>
>>>> Please share your thoughts.
>>>>
>>>> Thank you.
>>>>
>>>>
>>>>
>>>> ---------- Forwarded message ---------
>>>> From: Isuru Udana <is...@gmail.com>
>>>> Date: Thu, Dec 12, 2019 at 7:03 AM
>>>> Subject: Re: Positioning Synapse as an Integration Framework
>>>> To: <pr...@synapse.apache.org>
>>>>
>>>>
>>>> I will open this discussion to the community to reach a wide audience.
>>>>
>>>> On Wed, Dec 11, 2019 at 5:20 AM Vanjikumaran Sivajothy <
>>>> vanjikumaran@gmail.com> wrote:
>>>>
>>>>> I am not too sure about adopting the very abstract term Integration
>>>>> Framework; However, I can assure that moving towards container-native
>>>>> is a
>>>>> logical move.
>>>>> I can help on this to produce an initial set of artifacts.
>>>>>
>>>>>
>>>>>
>>>>> On Mon, Dec 2, 2019 at 4:23 PM Isuru Udana <is...@gmail.com> wrote:
>>>>>
>>>>> > Hi PMC,
>>>>> >
>>>>> > It has been 12 years since Synapse was founded (2007-12-19). As we
>>>>> all know
>>>>> > in the last few years we did not have a good run. The activity of the
>>>>> > project has significantly gone down and there is not much of a
>>>>> contribution
>>>>> > from the majority of the committers/PMC members.
>>>>> >
>>>>> > Also, ESB architectural style is no longer the preferred style for
>>>>> doing
>>>>> > the integration. The world has been moved towards container friendly
>>>>> > products, microservices, and cloud-native technologies. However, the
>>>>> > integration problem solved by the ESB architecture still exists and
>>>>> handled
>>>>> > by different entities.
>>>>> >
>>>>> > Even though Synapse is an ESB, it has most of the qualities (ex:
>>>>> faster
>>>>> > startup time, low resource consumption, etc.) that are important for
>>>>> > containers and microservices integrations. So with a little effort,
>>>>> we
>>>>> > could make Synapse a container friendly product that suits any
>>>>> > architectural style for doing the integration.
>>>>> >
>>>>> > So, should we consider positioning Synapse as an 'Integration
>>>>> Framework' or
>>>>> > an 'Integration Product' that serves all architectural styles?
>>>>> > Will that help us reactivate the project?
>>>>> >
>>>>> >
>>>>> > --
>>>>> > *Isuru Udana*
>>>>> >
>>>>> >
>>>>> >
>>>>> > *email: isudana@gmail.com <is...@gmail.com> blog:
>>>>> > http://mytecheye.blogspot.com/ <http://mytecheye.blogspot.com/>*
>>>>> >
>>>>>
>>>>>
>>>>> --
>>>>> Best Regards,
>>>>> Vanji
>>>>>
>>>>
>>>>
>>>> --
>>>> *Isuru Udana*
>>>> Senior Technical Lead
>>>>
>>>>
>>>>
>>>>
>>>> *; WSO2 Inc.; http://wso2.com <http://wso2.com>email: isudana@gmail.com
>>>> <is...@gmail.com> blog: http://mytecheye.blogspot.com/
>>>> <http://mytecheye.blogspot.com/>*
>>>>
>>>>
>>>>
>>>>
>
> --
> *Isuru Udana*
> Associate Director/Architect
>
>
>
> *; WSO2 Inc.; http://wso2.com <http://wso2.com>email: isudana@gmail.com
> <is...@gmail.com> *
>
>
>
Re: Positioning Synapse as an Integration Framework
Posted by Isuru Udana <is...@gmail.com>.
On Thu, Feb 13, 2020 at 8:53 PM Madhawa Kasun Gunasekara <
madhawa30@gmail.com> wrote:
> Hi All,
>
> Shall we start working on this? I believe there are so many things to
> improve. so let's start listing them. after that, we can prioritize items
> and create Jira tickets.
>
> +1. I will first work on integrating a build system (Travis or Jenkins)
for Pull Requests, that will make PR merging easier.
Thanks.
> Thanks,
> Madhawa
>
>
> On Tue, Jan 7, 2020 at 7:10 PM Madhawa Kasun Gunasekara <
> madhawa30@gmail.com> wrote:
>
>> +1,
>> Moving forward for the container friendly integration framework is a
>> great idea. How about considering for version 4.x.x. release. I can help
>> too.
>>
>> Thanks,
>> Madhawa
>>
>>
>> On Thu, Dec 12, 2019 at 2:38 AM Isuru Udana <is...@apache.org> wrote:
>>
>>> Hi All,
>>>
>>> It has been 12 years since Synapse was founded (2007-12-19). As we all
>>> know in the last few years we did not have a good run. The activity of the
>>> project has significantly gone down and there is not much of a contribution
>>> from the majority of the committers.
>>>
>>> Also, ESB architectural style is no longer the preferred style for doing
>>> the integration. The world has been moved towards container friendly
>>> products, microservices, and cloud-native technologies. However, the
>>> integration problem solved by the ESB architecture still exists and handled
>>> by different entities.
>>>
>>> Even though Synapse is an ESB, it has most of the qualities (ex: faster
>>> startup time, low resource consumption, etc.) that are important for
>>> containers and microservices integrations. So with a little effort, we
>>> could make Synapse a container friendly product that suits any
>>> architectural style for doing the integration.
>>>
>>> So, should we consider positioning Synapse as an 'Integration Framework'
>>> or an 'Integration Product' that serves all architectural styles?
>>> Will that help us reactivate the project?
>>>
>>> Please share your thoughts.
>>>
>>> Thank you.
>>>
>>>
>>>
>>> ---------- Forwarded message ---------
>>> From: Isuru Udana <is...@gmail.com>
>>> Date: Thu, Dec 12, 2019 at 7:03 AM
>>> Subject: Re: Positioning Synapse as an Integration Framework
>>> To: <pr...@synapse.apache.org>
>>>
>>>
>>> I will open this discussion to the community to reach a wide audience.
>>>
>>> On Wed, Dec 11, 2019 at 5:20 AM Vanjikumaran Sivajothy <
>>> vanjikumaran@gmail.com> wrote:
>>>
>>>> I am not too sure about adopting the very abstract term Integration
>>>> Framework; However, I can assure that moving towards container-native
>>>> is a
>>>> logical move.
>>>> I can help on this to produce an initial set of artifacts.
>>>>
>>>>
>>>>
>>>> On Mon, Dec 2, 2019 at 4:23 PM Isuru Udana <is...@gmail.com> wrote:
>>>>
>>>> > Hi PMC,
>>>> >
>>>> > It has been 12 years since Synapse was founded (2007-12-19). As we
>>>> all know
>>>> > in the last few years we did not have a good run. The activity of the
>>>> > project has significantly gone down and there is not much of a
>>>> contribution
>>>> > from the majority of the committers/PMC members.
>>>> >
>>>> > Also, ESB architectural style is no longer the preferred style for
>>>> doing
>>>> > the integration. The world has been moved towards container friendly
>>>> > products, microservices, and cloud-native technologies. However, the
>>>> > integration problem solved by the ESB architecture still exists and
>>>> handled
>>>> > by different entities.
>>>> >
>>>> > Even though Synapse is an ESB, it has most of the qualities (ex:
>>>> faster
>>>> > startup time, low resource consumption, etc.) that are important for
>>>> > containers and microservices integrations. So with a little effort, we
>>>> > could make Synapse a container friendly product that suits any
>>>> > architectural style for doing the integration.
>>>> >
>>>> > So, should we consider positioning Synapse as an 'Integration
>>>> Framework' or
>>>> > an 'Integration Product' that serves all architectural styles?
>>>> > Will that help us reactivate the project?
>>>> >
>>>> >
>>>> > --
>>>> > *Isuru Udana*
>>>> >
>>>> >
>>>> >
>>>> > *email: isudana@gmail.com <is...@gmail.com> blog:
>>>> > http://mytecheye.blogspot.com/ <http://mytecheye.blogspot.com/>*
>>>> >
>>>>
>>>>
>>>> --
>>>> Best Regards,
>>>> Vanji
>>>>
>>>
>>>
>>> --
>>> *Isuru Udana*
>>> Senior Technical Lead
>>>
>>>
>>>
>>>
>>> *; WSO2 Inc.; http://wso2.com <http://wso2.com>email: isudana@gmail.com
>>> <is...@gmail.com> blog: http://mytecheye.blogspot.com/
>>> <http://mytecheye.blogspot.com/>*
>>>
>>>
>>>
>>>
--
*Isuru Udana*
Associate Director/Architect
*; WSO2 Inc.; http://wso2.com <http://wso2.com>email: isudana@gmail.com
<is...@gmail.com> *
Re: Positioning Synapse as an Integration Framework
Posted by Madhawa Kasun Gunasekara <ma...@gmail.com>.
Hi All,
Shall we start working on this? I believe there are so many things to
improve. so let's start listing them. after that, we can prioritize items
and create Jira tickets.
Thanks,
Madhawa
On Tue, Jan 7, 2020 at 7:10 PM Madhawa Kasun Gunasekara <ma...@gmail.com>
wrote:
> +1,
> Moving forward for the container friendly integration framework is a great
> idea. How about considering for version 4.x.x. release. I can help too.
>
> Thanks,
> Madhawa
>
>
> On Thu, Dec 12, 2019 at 2:38 AM Isuru Udana <is...@apache.org> wrote:
>
>> Hi All,
>>
>> It has been 12 years since Synapse was founded (2007-12-19). As we all
>> know in the last few years we did not have a good run. The activity of the
>> project has significantly gone down and there is not much of a contribution
>> from the majority of the committers.
>>
>> Also, ESB architectural style is no longer the preferred style for doing
>> the integration. The world has been moved towards container friendly
>> products, microservices, and cloud-native technologies. However, the
>> integration problem solved by the ESB architecture still exists and handled
>> by different entities.
>>
>> Even though Synapse is an ESB, it has most of the qualities (ex: faster
>> startup time, low resource consumption, etc.) that are important for
>> containers and microservices integrations. So with a little effort, we
>> could make Synapse a container friendly product that suits any
>> architectural style for doing the integration.
>>
>> So, should we consider positioning Synapse as an 'Integration Framework'
>> or an 'Integration Product' that serves all architectural styles?
>> Will that help us reactivate the project?
>>
>> Please share your thoughts.
>>
>> Thank you.
>>
>>
>>
>> ---------- Forwarded message ---------
>> From: Isuru Udana <is...@gmail.com>
>> Date: Thu, Dec 12, 2019 at 7:03 AM
>> Subject: Re: Positioning Synapse as an Integration Framework
>> To: <pr...@synapse.apache.org>
>>
>>
>> I will open this discussion to the community to reach a wide audience.
>>
>> On Wed, Dec 11, 2019 at 5:20 AM Vanjikumaran Sivajothy <
>> vanjikumaran@gmail.com> wrote:
>>
>>> I am not too sure about adopting the very abstract term Integration
>>> Framework; However, I can assure that moving towards container-native is
>>> a
>>> logical move.
>>> I can help on this to produce an initial set of artifacts.
>>>
>>>
>>>
>>> On Mon, Dec 2, 2019 at 4:23 PM Isuru Udana <is...@gmail.com> wrote:
>>>
>>> > Hi PMC,
>>> >
>>> > It has been 12 years since Synapse was founded (2007-12-19). As we all
>>> know
>>> > in the last few years we did not have a good run. The activity of the
>>> > project has significantly gone down and there is not much of a
>>> contribution
>>> > from the majority of the committers/PMC members.
>>> >
>>> > Also, ESB architectural style is no longer the preferred style for
>>> doing
>>> > the integration. The world has been moved towards container friendly
>>> > products, microservices, and cloud-native technologies. However, the
>>> > integration problem solved by the ESB architecture still exists and
>>> handled
>>> > by different entities.
>>> >
>>> > Even though Synapse is an ESB, it has most of the qualities (ex: faster
>>> > startup time, low resource consumption, etc.) that are important for
>>> > containers and microservices integrations. So with a little effort, we
>>> > could make Synapse a container friendly product that suits any
>>> > architectural style for doing the integration.
>>> >
>>> > So, should we consider positioning Synapse as an 'Integration
>>> Framework' or
>>> > an 'Integration Product' that serves all architectural styles?
>>> > Will that help us reactivate the project?
>>> >
>>> >
>>> > --
>>> > *Isuru Udana*
>>> >
>>> >
>>> >
>>> > *email: isudana@gmail.com <is...@gmail.com> blog:
>>> > http://mytecheye.blogspot.com/ <http://mytecheye.blogspot.com/>*
>>> >
>>>
>>>
>>> --
>>> Best Regards,
>>> Vanji
>>>
>>
>>
>> --
>> *Isuru Udana*
>> Senior Technical Lead
>>
>>
>>
>>
>> *; WSO2 Inc.; http://wso2.com <http://wso2.com>email: isudana@gmail.com
>> <is...@gmail.com> blog: http://mytecheye.blogspot.com/
>> <http://mytecheye.blogspot.com/>*
>>
>>
>>
>>