You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@pulsar.apache.org by Yu <li...@apache.org> on 2022/04/18 10:35:54 UTC
Categorize Pulsar Plugins
Hi Pulsarers,
For the Ecosystem Page [1], we want to make it a place for the Pulsar
community to come together and share the components the community needs to
build better streaming data pipelines and event-driven applications.
So I've collected all Pulsar-related plugins and tried to re-categorize
them **based on scenarios**.
For the "Components Managed by DataStax", does anyone can help review the
"Category"? [2] We're unsure about it.
Feel free to review the whole sheet and comment if I miss or misunderstand
anything, thank you!
[1] https://pulsar-next.staged.apache.org/ecosystem/
[2]
https://docs.google.com/spreadsheets/d/1n4oAQx_hxBaEYkHiVVRVTVpOKfE26i4am6UYieriXYQ/edit#gid=0
Anonymitaet
Re: Categorize Pulsar Plugins
Posted by Yu <li...@apache.org>.
OK, thanks for your explanation, Chris.
FYI: I've organized all components around Pulsar here:
https://docs.google.com/spreadsheets/d/1n4oAQx_hxBaEYkHiVVRVTVpOKfE26i4am6UYieriXYQ/edit#gid=1261350388
On Wed, Apr 20, 2022 at 11:48 PM Chris Bartholomew <
chris.bartholomew@kesque.com> wrote:
> Hi Anonymitaet,
>
> On 1, Starlight for JMS is technically a wrapper around the Java API.
> However, JMS is a widely used client API specification so to call it a
> client wrapper doesn't seem like the right classification to me. The Python
> client is a wrapper around the C client, but we don't call that a client
> wrapper, is called the Python client.
>
> On 2, I agree it makes sense to call it a "Security Plugin".
>
> Thanks,
> Chris
>
> On Wed, 20 Apr 2022 at 01:06, Yu <li...@apache.org> wrote:
>
>> Hi Chris,
>>
>> Thank you very much for providing useful information! I've added them all
>> to the sheet.
>>
>> For categories, I have two quick questions:
>>
>> #1. For Starlight for JMS [1]
>> I see you categorize it as "Client API". Does it make sense to categorize
>> it as "Client Wrapper"? (which is the same as the Kafka Client Wrapper [2])
>>
>> #2. For OpenID Connect Authentication Plugin [3]
>> I see you categorize it as "Authentication Plugin". Does it make sense to
>> categorize it as "Security Plugin"? It is more general and "extendable"
>> since we can include more security-related plugins (eg.
>> authentication/authorization plugins) in the future.
>>
>> Let me know what you think, thanks!
>>
>> [1] https://github.com/datastax/pulsar-jms
>> [2]
>> https://github.com/apache/pulsar-adapters/tree/master/pulsar-client-kafka-compat
>> [3] https://github.com/datastax/pulsar-openid-connect-plugin
>>
>> Anonymitaet
>>
>> On Wed, Apr 20, 2022 at 2:08 AM Chris Bartholomew <
>> chris.bartholomew@kesque.com> wrote:
>>
>>> Hi Anonymitaet,
>>>
>>> I provided input on the "Components Managed by DataStax" as a comment
>>> in the Google doc. If you need any more information, please let me know.
>>>
>>> Cheers,
>>> Chris
>>>
>>>
>>> On Mon, 18 Apr 2022 at 06:36, Yu <li...@apache.org> wrote:
>>>
>>>> Hi Pulsarers,
>>>>
>>>>
>>>> For the Ecosystem Page [1], we want to make it a place for the Pulsar
>>>> community to come together and share the components the community needs to
>>>> build better streaming data pipelines and event-driven applications.
>>>>
>>>>
>>>> So I've collected all Pulsar-related plugins and tried to re-categorize
>>>> them **based on scenarios**.
>>>>
>>>>
>>>> For the "Components Managed by DataStax", does anyone can help review
>>>> the "Category"? [2] We're unsure about it.
>>>>
>>>>
>>>> Feel free to review the whole sheet and comment if I miss or
>>>> misunderstand anything, thank you!
>>>>
>>>>
>>>> [1] https://pulsar-next.staged.apache.org/ecosystem/
>>>>
>>>> [2]
>>>> https://docs.google.com/spreadsheets/d/1n4oAQx_hxBaEYkHiVVRVTVpOKfE26i4am6UYieriXYQ/edit#gid=0
>>>>
>>>>
>>>> Anonymitaet
>>>>
>>>>
>>>>
Re: Categorize Pulsar Plugins
Posted by Yu <li...@apache.org>.
OK, thanks for your explanation, Chris.
FYI: I've organized all components around Pulsar here:
https://docs.google.com/spreadsheets/d/1n4oAQx_hxBaEYkHiVVRVTVpOKfE26i4am6UYieriXYQ/edit#gid=1261350388
On Wed, Apr 20, 2022 at 11:48 PM Chris Bartholomew <
chris.bartholomew@kesque.com> wrote:
> Hi Anonymitaet,
>
> On 1, Starlight for JMS is technically a wrapper around the Java API.
> However, JMS is a widely used client API specification so to call it a
> client wrapper doesn't seem like the right classification to me. The Python
> client is a wrapper around the C client, but we don't call that a client
> wrapper, is called the Python client.
>
> On 2, I agree it makes sense to call it a "Security Plugin".
>
> Thanks,
> Chris
>
> On Wed, 20 Apr 2022 at 01:06, Yu <li...@apache.org> wrote:
>
>> Hi Chris,
>>
>> Thank you very much for providing useful information! I've added them all
>> to the sheet.
>>
>> For categories, I have two quick questions:
>>
>> #1. For Starlight for JMS [1]
>> I see you categorize it as "Client API". Does it make sense to categorize
>> it as "Client Wrapper"? (which is the same as the Kafka Client Wrapper [2])
>>
>> #2. For OpenID Connect Authentication Plugin [3]
>> I see you categorize it as "Authentication Plugin". Does it make sense to
>> categorize it as "Security Plugin"? It is more general and "extendable"
>> since we can include more security-related plugins (eg.
>> authentication/authorization plugins) in the future.
>>
>> Let me know what you think, thanks!
>>
>> [1] https://github.com/datastax/pulsar-jms
>> [2]
>> https://github.com/apache/pulsar-adapters/tree/master/pulsar-client-kafka-compat
>> [3] https://github.com/datastax/pulsar-openid-connect-plugin
>>
>> Anonymitaet
>>
>> On Wed, Apr 20, 2022 at 2:08 AM Chris Bartholomew <
>> chris.bartholomew@kesque.com> wrote:
>>
>>> Hi Anonymitaet,
>>>
>>> I provided input on the "Components Managed by DataStax" as a comment
>>> in the Google doc. If you need any more information, please let me know.
>>>
>>> Cheers,
>>> Chris
>>>
>>>
>>> On Mon, 18 Apr 2022 at 06:36, Yu <li...@apache.org> wrote:
>>>
>>>> Hi Pulsarers,
>>>>
>>>>
>>>> For the Ecosystem Page [1], we want to make it a place for the Pulsar
>>>> community to come together and share the components the community needs to
>>>> build better streaming data pipelines and event-driven applications.
>>>>
>>>>
>>>> So I've collected all Pulsar-related plugins and tried to re-categorize
>>>> them **based on scenarios**.
>>>>
>>>>
>>>> For the "Components Managed by DataStax", does anyone can help review
>>>> the "Category"? [2] We're unsure about it.
>>>>
>>>>
>>>> Feel free to review the whole sheet and comment if I miss or
>>>> misunderstand anything, thank you!
>>>>
>>>>
>>>> [1] https://pulsar-next.staged.apache.org/ecosystem/
>>>>
>>>> [2]
>>>> https://docs.google.com/spreadsheets/d/1n4oAQx_hxBaEYkHiVVRVTVpOKfE26i4am6UYieriXYQ/edit#gid=0
>>>>
>>>>
>>>> Anonymitaet
>>>>
>>>>
>>>>
Re: Categorize Pulsar Plugins
Posted by Chris Bartholomew <ch...@kesque.com>.
Hi Anonymitaet,
On 1, Starlight for JMS is technically a wrapper around the Java API.
However, JMS is a widely used client API specification so to call it a
client wrapper doesn't seem like the right classification to me. The Python
client is a wrapper around the C client, but we don't call that a client
wrapper, is called the Python client.
On 2, I agree it makes sense to call it a "Security Plugin".
Thanks,
Chris
On Wed, 20 Apr 2022 at 01:06, Yu <li...@apache.org> wrote:
> Hi Chris,
>
> Thank you very much for providing useful information! I've added them all
> to the sheet.
>
> For categories, I have two quick questions:
>
> #1. For Starlight for JMS [1]
> I see you categorize it as "Client API". Does it make sense to categorize
> it as "Client Wrapper"? (which is the same as the Kafka Client Wrapper [2])
>
> #2. For OpenID Connect Authentication Plugin [3]
> I see you categorize it as "Authentication Plugin". Does it make sense to
> categorize it as "Security Plugin"? It is more general and "extendable"
> since we can include more security-related plugins (eg.
> authentication/authorization plugins) in the future.
>
> Let me know what you think, thanks!
>
> [1] https://github.com/datastax/pulsar-jms
> [2]
> https://github.com/apache/pulsar-adapters/tree/master/pulsar-client-kafka-compat
> [3] https://github.com/datastax/pulsar-openid-connect-plugin
>
> Anonymitaet
>
> On Wed, Apr 20, 2022 at 2:08 AM Chris Bartholomew <
> chris.bartholomew@kesque.com> wrote:
>
>> Hi Anonymitaet,
>>
>> I provided input on the "Components Managed by DataStax" as a comment
>> in the Google doc. If you need any more information, please let me know.
>>
>> Cheers,
>> Chris
>>
>>
>> On Mon, 18 Apr 2022 at 06:36, Yu <li...@apache.org> wrote:
>>
>>> Hi Pulsarers,
>>>
>>>
>>> For the Ecosystem Page [1], we want to make it a place for the Pulsar
>>> community to come together and share the components the community needs to
>>> build better streaming data pipelines and event-driven applications.
>>>
>>>
>>> So I've collected all Pulsar-related plugins and tried to re-categorize
>>> them **based on scenarios**.
>>>
>>>
>>> For the "Components Managed by DataStax", does anyone can help review
>>> the "Category"? [2] We're unsure about it.
>>>
>>>
>>> Feel free to review the whole sheet and comment if I miss or
>>> misunderstand anything, thank you!
>>>
>>>
>>> [1] https://pulsar-next.staged.apache.org/ecosystem/
>>>
>>> [2]
>>> https://docs.google.com/spreadsheets/d/1n4oAQx_hxBaEYkHiVVRVTVpOKfE26i4am6UYieriXYQ/edit#gid=0
>>>
>>>
>>> Anonymitaet
>>>
>>>
>>>
Re: Categorize Pulsar Plugins
Posted by Chris Bartholomew <ch...@kesque.com>.
Hi Anonymitaet,
On 1, Starlight for JMS is technically a wrapper around the Java API.
However, JMS is a widely used client API specification so to call it a
client wrapper doesn't seem like the right classification to me. The Python
client is a wrapper around the C client, but we don't call that a client
wrapper, is called the Python client.
On 2, I agree it makes sense to call it a "Security Plugin".
Thanks,
Chris
On Wed, 20 Apr 2022 at 01:06, Yu <li...@apache.org> wrote:
> Hi Chris,
>
> Thank you very much for providing useful information! I've added them all
> to the sheet.
>
> For categories, I have two quick questions:
>
> #1. For Starlight for JMS [1]
> I see you categorize it as "Client API". Does it make sense to categorize
> it as "Client Wrapper"? (which is the same as the Kafka Client Wrapper [2])
>
> #2. For OpenID Connect Authentication Plugin [3]
> I see you categorize it as "Authentication Plugin". Does it make sense to
> categorize it as "Security Plugin"? It is more general and "extendable"
> since we can include more security-related plugins (eg.
> authentication/authorization plugins) in the future.
>
> Let me know what you think, thanks!
>
> [1] https://github.com/datastax/pulsar-jms
> [2]
> https://github.com/apache/pulsar-adapters/tree/master/pulsar-client-kafka-compat
> [3] https://github.com/datastax/pulsar-openid-connect-plugin
>
> Anonymitaet
>
> On Wed, Apr 20, 2022 at 2:08 AM Chris Bartholomew <
> chris.bartholomew@kesque.com> wrote:
>
>> Hi Anonymitaet,
>>
>> I provided input on the "Components Managed by DataStax" as a comment
>> in the Google doc. If you need any more information, please let me know.
>>
>> Cheers,
>> Chris
>>
>>
>> On Mon, 18 Apr 2022 at 06:36, Yu <li...@apache.org> wrote:
>>
>>> Hi Pulsarers,
>>>
>>>
>>> For the Ecosystem Page [1], we want to make it a place for the Pulsar
>>> community to come together and share the components the community needs to
>>> build better streaming data pipelines and event-driven applications.
>>>
>>>
>>> So I've collected all Pulsar-related plugins and tried to re-categorize
>>> them **based on scenarios**.
>>>
>>>
>>> For the "Components Managed by DataStax", does anyone can help review
>>> the "Category"? [2] We're unsure about it.
>>>
>>>
>>> Feel free to review the whole sheet and comment if I miss or
>>> misunderstand anything, thank you!
>>>
>>>
>>> [1] https://pulsar-next.staged.apache.org/ecosystem/
>>>
>>> [2]
>>> https://docs.google.com/spreadsheets/d/1n4oAQx_hxBaEYkHiVVRVTVpOKfE26i4am6UYieriXYQ/edit#gid=0
>>>
>>>
>>> Anonymitaet
>>>
>>>
>>>
Re: Categorize Pulsar Plugins
Posted by Yu <li...@apache.org>.
Hi Chris,
Thank you very much for providing useful information! I've added them all
to the sheet.
For categories, I have two quick questions:
#1. For Starlight for JMS [1]
I see you categorize it as "Client API". Does it make sense to categorize
it as "Client Wrapper"? (which is the same as the Kafka Client Wrapper [2])
#2. For OpenID Connect Authentication Plugin [3]
I see you categorize it as "Authentication Plugin". Does it make sense to
categorize it as "Security Plugin"? It is more general and "extendable"
since we can include more security-related plugins (eg.
authentication/authorization plugins) in the future.
Let me know what you think, thanks!
[1] https://github.com/datastax/pulsar-jms
[2]
https://github.com/apache/pulsar-adapters/tree/master/pulsar-client-kafka-compat
[3] https://github.com/datastax/pulsar-openid-connect-plugin
Anonymitaet
On Wed, Apr 20, 2022 at 2:08 AM Chris Bartholomew <
chris.bartholomew@kesque.com> wrote:
> Hi Anonymitaet,
>
> I provided input on the "Components Managed by DataStax" as a comment in
> the Google doc. If you need any more information, please let me know.
>
> Cheers,
> Chris
>
>
> On Mon, 18 Apr 2022 at 06:36, Yu <li...@apache.org> wrote:
>
>> Hi Pulsarers,
>>
>>
>> For the Ecosystem Page [1], we want to make it a place for the Pulsar
>> community to come together and share the components the community needs to
>> build better streaming data pipelines and event-driven applications.
>>
>>
>> So I've collected all Pulsar-related plugins and tried to re-categorize
>> them **based on scenarios**.
>>
>>
>> For the "Components Managed by DataStax", does anyone can help review the
>> "Category"? [2] We're unsure about it.
>>
>>
>> Feel free to review the whole sheet and comment if I miss or
>> misunderstand anything, thank you!
>>
>>
>> [1] https://pulsar-next.staged.apache.org/ecosystem/
>>
>> [2]
>> https://docs.google.com/spreadsheets/d/1n4oAQx_hxBaEYkHiVVRVTVpOKfE26i4am6UYieriXYQ/edit#gid=0
>>
>>
>> Anonymitaet
>>
>>
>>
Re: Categorize Pulsar Plugins
Posted by Yu <li...@apache.org>.
Hi Chris,
Thank you very much for providing useful information! I've added them all
to the sheet.
For categories, I have two quick questions:
#1. For Starlight for JMS [1]
I see you categorize it as "Client API". Does it make sense to categorize
it as "Client Wrapper"? (which is the same as the Kafka Client Wrapper [2])
#2. For OpenID Connect Authentication Plugin [3]
I see you categorize it as "Authentication Plugin". Does it make sense to
categorize it as "Security Plugin"? It is more general and "extendable"
since we can include more security-related plugins (eg.
authentication/authorization plugins) in the future.
Let me know what you think, thanks!
[1] https://github.com/datastax/pulsar-jms
[2]
https://github.com/apache/pulsar-adapters/tree/master/pulsar-client-kafka-compat
[3] https://github.com/datastax/pulsar-openid-connect-plugin
Anonymitaet
On Wed, Apr 20, 2022 at 2:08 AM Chris Bartholomew <
chris.bartholomew@kesque.com> wrote:
> Hi Anonymitaet,
>
> I provided input on the "Components Managed by DataStax" as a comment in
> the Google doc. If you need any more information, please let me know.
>
> Cheers,
> Chris
>
>
> On Mon, 18 Apr 2022 at 06:36, Yu <li...@apache.org> wrote:
>
>> Hi Pulsarers,
>>
>>
>> For the Ecosystem Page [1], we want to make it a place for the Pulsar
>> community to come together and share the components the community needs to
>> build better streaming data pipelines and event-driven applications.
>>
>>
>> So I've collected all Pulsar-related plugins and tried to re-categorize
>> them **based on scenarios**.
>>
>>
>> For the "Components Managed by DataStax", does anyone can help review the
>> "Category"? [2] We're unsure about it.
>>
>>
>> Feel free to review the whole sheet and comment if I miss or
>> misunderstand anything, thank you!
>>
>>
>> [1] https://pulsar-next.staged.apache.org/ecosystem/
>>
>> [2]
>> https://docs.google.com/spreadsheets/d/1n4oAQx_hxBaEYkHiVVRVTVpOKfE26i4am6UYieriXYQ/edit#gid=0
>>
>>
>> Anonymitaet
>>
>>
>>
Re: Categorize Pulsar Plugins
Posted by Chris Bartholomew <ch...@kesque.com>.
Hi Anonymitaet,
I provided input on the "Components Managed by DataStax" as a comment in
the Google doc. If you need any more information, please let me know.
Cheers,
Chris
On Mon, 18 Apr 2022 at 06:36, Yu <li...@apache.org> wrote:
> Hi Pulsarers,
>
>
> For the Ecosystem Page [1], we want to make it a place for the Pulsar
> community to come together and share the components the community needs to
> build better streaming data pipelines and event-driven applications.
>
>
> So I've collected all Pulsar-related plugins and tried to re-categorize
> them **based on scenarios**.
>
>
> For the "Components Managed by DataStax", does anyone can help review the
> "Category"? [2] We're unsure about it.
>
>
> Feel free to review the whole sheet and comment if I miss or misunderstand
> anything, thank you!
>
>
> [1] https://pulsar-next.staged.apache.org/ecosystem/
>
> [2]
> https://docs.google.com/spreadsheets/d/1n4oAQx_hxBaEYkHiVVRVTVpOKfE26i4am6UYieriXYQ/edit#gid=0
>
>
> Anonymitaet
>
>
>