You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by Romain Manni-Bucau <rm...@gmail.com> on 2020/08/10 06:47:02 UTC
Re: Fork some of our MP impls
Small up, guess it is still holidays so will wait for a few more weeks to
try to get more feedbacks before doing anything.
Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> | Blog
<https://rmannibucau.metawerx.net/> | Old Blog
<http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> |
LinkedIn <https://www.linkedin.com/in/rmannibucau> | Book
<https://www.packtpub.com/application-development/java-ee-8-high-performance>
Le ven. 31 juil. 2020 à 09:16, Romain Manni-Bucau <rm...@gmail.com> a
écrit :
> Makes sense, thanks François
>
> Romain Manni-Bucau
> @rmannibucau <https://twitter.com/rmannibucau> | Blog
> <https://rmannibucau.metawerx.net/> | Old Blog
> <http://rmannibucau.wordpress.com> | Github
> <https://github.com/rmannibucau> | LinkedIn
> <https://www.linkedin.com/in/rmannibucau> | Book
> <https://www.packtpub.com/application-development/java-ee-8-high-performance>
>
>
> Le ven. 31 juil. 2020 à 09:15, Francois Papon <
> francois.papon@openobject.fr> a écrit :
>
>> Hi Romain,
>>
>> I think the config spec is interesting and could be add to the list.
>>
>> regards,
>>
>> Françoisfpapon@apache.org
>>
>> Le 31/07/2020 à 08:34, Romain Manni-Bucau a écrit :
>>
>> Hi everyone,
>>
>> After some years of MP I think it is not a safe enough technology for
>> long term applications - i.e. maintained and evolved, not just
>> developed for 6 months.
>> The main drawback is that it changes and breaks too often and from my
>> understanding it is not likely about to change (what I understood is it
>> will likely be worse and can even import vendor/library API in the spec API
>> as it had been done for tracing one).
>>
>> The most common requirements are, IMHO:
>>
>> 1. health
>> 2. metrics (gauge+counter+openmetrics exporter, others are fancy things)
>> 3. tracing
>>
>> maybe jwt-auth even if less sure.
>>
>> Therefore I wonder if we want to fork our own MP impl to provide these 3
>> specs simplified versions with a stable API.
>> I envision a single repo with the 3 api/impl.
>>
>> wdyt?
>>
>> Romain Manni-Bucau
>> @rmannibucau <https://twitter.com/rmannibucau> | Blog
>> <https://rmannibucau.metawerx.net/> | Old Blog
>> <http://rmannibucau.wordpress.com> | Github
>> <https://github.com/rmannibucau> | LinkedIn
>> <https://www.linkedin.com/in/rmannibucau> | Book
>> <https://www.packtpub.com/application-development/java-ee-8-high-performance>
>>
>>
Re: Fork some of our MP impls
Posted by Romain Manni-Bucau <rm...@gmail.com>.
Interesting feedback from a MP leader ([1]) leading me back to this thread.
Not sure I'm wrong but it looks like they don't care (know how?) making it
a proper spec so I'd like to up this thread.
Think we can start by extracting:
1. config (org.apache.geronimo.stack.config package?) - and adding native
pojo mapping + @Doc(value) maybe?
2. health (org.apache.geronimo.stack.health) - making it
reactive/CompletionStage friendly for remote checks probably
3. tracing (o.a.g.s.tracing) - probably cutting the opentracing dependeny
to use our own package too and ensuring it is reactive friendly
4. metrics (o.a.g.s.metrics)
5. mp-jwt maybe
wdyt?
Any project idea? geronimo-software-stack?
[1]
https://github.com/eclipse/microprofile/issues/50#issuecomment-744598911
Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> | Blog
<https://rmannibucau.metawerx.net/> | Old Blog
<http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> |
LinkedIn <https://www.linkedin.com/in/rmannibucau> | Book
<https://www.packtpub.com/application-development/java-ee-8-high-performance>
Le ven. 16 oct. 2020 à 14:57, Romain Manni-Bucau <rm...@gmail.com> a
écrit :
> Just to comfort this thread, openapi 2.RC breaks API and behaviors too +
> can be worth having a POJO mapping to simplify the JSON usage (and
> reusability since it avoids customizations and custom, provider specific
> factories).
> So overall I think that rather than sticking to Microprofile which does
> not go anywhere we should keep our codebase as something independent,
> stable and reusable.
>
> Romain Manni-Bucau
> @rmannibucau <https://twitter.com/rmannibucau> | Blog
> <https://rmannibucau.metawerx.net/> | Old Blog
> <http://rmannibucau.wordpress.com> | Github
> <https://github.com/rmannibucau> | LinkedIn
> <https://www.linkedin.com/in/rmannibucau> | Book
> <https://www.packtpub.com/application-development/java-ee-8-high-performance>
>
>
> Le mar. 22 sept. 2020 à 20:53, Francois Papon <
> francois.papon@openobject.fr> a écrit :
>
>> No problem, I don't care so much about the name too ;)
>>
>> regards,
>>
>> Françoisfpapon@apache.org
>>
>> Le 22/09/2020 à 20:01, Romain Manni-Bucau a écrit :
>>
>> Hmm, both are not linked this way (more the opposite ;)).
>> Why not kat (cat for kubernetes, read somewhere everybody loves cats)? ;)
>>
>> Btw i dont care much of the name while it can last but Id like some other
>> opinion if possible (even negative) - otherwise it can be done at github ;).
>>
>> Le mar. 22 sept. 2020 à 19:34, Francois Papon <
>> francois.papon@openobject.fr> a écrit :
>>
>>> May be we can call it "excalibur" as we already have "arthur" :)
>>>
>>> regards,
>>>
>>> Françoisfpapon@apache.org
>>>
>>> Le 21/09/2020 à 21:05, Romain Manni-Bucau a écrit :
>>>
>>> Up, any issue to create a geronimo-stack (happy to get a better name)
>>> project?
>>>
>>>
>>> Le lun. 10 août 2020 à 08:47, Romain Manni-Bucau <rm...@gmail.com>
>>> a écrit :
>>>
>>>> Small up, guess it is still holidays so will wait for a few more weeks
>>>> to try to get more feedbacks before doing anything.
>>>>
>>>> Romain Manni-Bucau
>>>> @rmannibucau <https://twitter.com/rmannibucau> | Blog
>>>> <https://rmannibucau.metawerx.net/> | Old Blog
>>>> <http://rmannibucau.wordpress.com> | Github
>>>> <https://github.com/rmannibucau> | LinkedIn
>>>> <https://www.linkedin.com/in/rmannibucau> | Book
>>>> <https://www.packtpub.com/application-development/java-ee-8-high-performance>
>>>>
>>>>
>>>> Le ven. 31 juil. 2020 à 09:16, Romain Manni-Bucau <
>>>> rmannibucau@gmail.com> a écrit :
>>>>
>>>>> Makes sense, thanks François
>>>>>
>>>>> Romain Manni-Bucau
>>>>> @rmannibucau <https://twitter.com/rmannibucau> | Blog
>>>>> <https://rmannibucau.metawerx.net/> | Old Blog
>>>>> <http://rmannibucau.wordpress.com> | Github
>>>>> <https://github.com/rmannibucau> | LinkedIn
>>>>> <https://www.linkedin.com/in/rmannibucau> | Book
>>>>> <https://www.packtpub.com/application-development/java-ee-8-high-performance>
>>>>>
>>>>>
>>>>> Le ven. 31 juil. 2020 à 09:15, Francois Papon <
>>>>> francois.papon@openobject.fr> a écrit :
>>>>>
>>>>>> Hi Romain,
>>>>>>
>>>>>> I think the config spec is interesting and could be add to the list.
>>>>>>
>>>>>> regards,
>>>>>>
>>>>>> Françoisfpapon@apache.org
>>>>>>
>>>>>> Le 31/07/2020 à 08:34, Romain Manni-Bucau a écrit :
>>>>>>
>>>>>> Hi everyone,
>>>>>>
>>>>>> After some years of MP I think it is not a safe enough technology for
>>>>>> long term applications - i.e. maintained and evolved, not just
>>>>>> developed for 6 months.
>>>>>> The main drawback is that it changes and breaks too often and from my
>>>>>> understanding it is not likely about to change (what I understood is it
>>>>>> will likely be worse and can even import vendor/library API in the spec API
>>>>>> as it had been done for tracing one).
>>>>>>
>>>>>> The most common requirements are, IMHO:
>>>>>>
>>>>>> 1. health
>>>>>> 2. metrics (gauge+counter+openmetrics exporter, others are fancy
>>>>>> things)
>>>>>> 3. tracing
>>>>>>
>>>>>> maybe jwt-auth even if less sure.
>>>>>>
>>>>>> Therefore I wonder if we want to fork our own MP impl to provide
>>>>>> these 3 specs simplified versions with a stable API.
>>>>>> I envision a single repo with the 3 api/impl.
>>>>>>
>>>>>> wdyt?
>>>>>>
>>>>>> Romain Manni-Bucau
>>>>>> @rmannibucau <https://twitter.com/rmannibucau> | Blog
>>>>>> <https://rmannibucau.metawerx.net/> | Old Blog
>>>>>> <http://rmannibucau.wordpress.com> | Github
>>>>>> <https://github.com/rmannibucau> | LinkedIn
>>>>>> <https://www.linkedin.com/in/rmannibucau> | Book
>>>>>> <https://www.packtpub.com/application-development/java-ee-8-high-performance>
>>>>>>
>>>>>>
Re: Fork some of our MP impls
Posted by Romain Manni-Bucau <rm...@gmail.com>.
Just to comfort this thread, openapi 2.RC breaks API and behaviors too +
can be worth having a POJO mapping to simplify the JSON usage (and
reusability since it avoids customizations and custom, provider specific
factories).
So overall I think that rather than sticking to Microprofile which does not
go anywhere we should keep our codebase as something independent, stable
and reusable.
Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> | Blog
<https://rmannibucau.metawerx.net/> | Old Blog
<http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> |
LinkedIn <https://www.linkedin.com/in/rmannibucau> | Book
<https://www.packtpub.com/application-development/java-ee-8-high-performance>
Le mar. 22 sept. 2020 à 20:53, Francois Papon <fr...@openobject.fr>
a écrit :
> No problem, I don't care so much about the name too ;)
>
> regards,
>
> Françoisfpapon@apache.org
>
> Le 22/09/2020 à 20:01, Romain Manni-Bucau a écrit :
>
> Hmm, both are not linked this way (more the opposite ;)).
> Why not kat (cat for kubernetes, read somewhere everybody loves cats)? ;)
>
> Btw i dont care much of the name while it can last but Id like some other
> opinion if possible (even negative) - otherwise it can be done at github ;).
>
> Le mar. 22 sept. 2020 à 19:34, Francois Papon <
> francois.papon@openobject.fr> a écrit :
>
>> May be we can call it "excalibur" as we already have "arthur" :)
>>
>> regards,
>>
>> Françoisfpapon@apache.org
>>
>> Le 21/09/2020 à 21:05, Romain Manni-Bucau a écrit :
>>
>> Up, any issue to create a geronimo-stack (happy to get a better name)
>> project?
>>
>>
>> Le lun. 10 août 2020 à 08:47, Romain Manni-Bucau <rm...@gmail.com>
>> a écrit :
>>
>>> Small up, guess it is still holidays so will wait for a few more weeks
>>> to try to get more feedbacks before doing anything.
>>>
>>> Romain Manni-Bucau
>>> @rmannibucau <https://twitter.com/rmannibucau> | Blog
>>> <https://rmannibucau.metawerx.net/> | Old Blog
>>> <http://rmannibucau.wordpress.com> | Github
>>> <https://github.com/rmannibucau> | LinkedIn
>>> <https://www.linkedin.com/in/rmannibucau> | Book
>>> <https://www.packtpub.com/application-development/java-ee-8-high-performance>
>>>
>>>
>>> Le ven. 31 juil. 2020 à 09:16, Romain Manni-Bucau <rm...@gmail.com>
>>> a écrit :
>>>
>>>> Makes sense, thanks François
>>>>
>>>> Romain Manni-Bucau
>>>> @rmannibucau <https://twitter.com/rmannibucau> | Blog
>>>> <https://rmannibucau.metawerx.net/> | Old Blog
>>>> <http://rmannibucau.wordpress.com> | Github
>>>> <https://github.com/rmannibucau> | LinkedIn
>>>> <https://www.linkedin.com/in/rmannibucau> | Book
>>>> <https://www.packtpub.com/application-development/java-ee-8-high-performance>
>>>>
>>>>
>>>> Le ven. 31 juil. 2020 à 09:15, Francois Papon <
>>>> francois.papon@openobject.fr> a écrit :
>>>>
>>>>> Hi Romain,
>>>>>
>>>>> I think the config spec is interesting and could be add to the list.
>>>>>
>>>>> regards,
>>>>>
>>>>> Françoisfpapon@apache.org
>>>>>
>>>>> Le 31/07/2020 à 08:34, Romain Manni-Bucau a écrit :
>>>>>
>>>>> Hi everyone,
>>>>>
>>>>> After some years of MP I think it is not a safe enough technology for
>>>>> long term applications - i.e. maintained and evolved, not just
>>>>> developed for 6 months.
>>>>> The main drawback is that it changes and breaks too often and from my
>>>>> understanding it is not likely about to change (what I understood is it
>>>>> will likely be worse and can even import vendor/library API in the spec API
>>>>> as it had been done for tracing one).
>>>>>
>>>>> The most common requirements are, IMHO:
>>>>>
>>>>> 1. health
>>>>> 2. metrics (gauge+counter+openmetrics exporter, others are fancy
>>>>> things)
>>>>> 3. tracing
>>>>>
>>>>> maybe jwt-auth even if less sure.
>>>>>
>>>>> Therefore I wonder if we want to fork our own MP impl to provide these
>>>>> 3 specs simplified versions with a stable API.
>>>>> I envision a single repo with the 3 api/impl.
>>>>>
>>>>> wdyt?
>>>>>
>>>>> Romain Manni-Bucau
>>>>> @rmannibucau <https://twitter.com/rmannibucau> | Blog
>>>>> <https://rmannibucau.metawerx.net/> | Old Blog
>>>>> <http://rmannibucau.wordpress.com> | Github
>>>>> <https://github.com/rmannibucau> | LinkedIn
>>>>> <https://www.linkedin.com/in/rmannibucau> | Book
>>>>> <https://www.packtpub.com/application-development/java-ee-8-high-performance>
>>>>>
>>>>>
Re: Fork some of our MP impls
Posted by Francois Papon <fr...@openobject.fr>.
No problem, I don't care so much about the name too ;)
regards,
François
fpapon@apache.org
Le 22/09/2020 à 20:01, Romain Manni-Bucau a écrit :
> Hmm, both are not linked this way (more the opposite ;)).
> Why not kat (cat for kubernetes, read somewhere everybody loves cats)? ;)
>
> Btw i dont care much of the name while it can last but Id like some
> other opinion if possible (even negative) - otherwise it can be done
> at github ;).
>
> Le mar. 22 sept. 2020 à 19:34, Francois Papon
> <francois.papon@openobject.fr <ma...@openobject.fr>> a
> écrit :
>
> May be we can call it "excalibur" as we already have "arthur" :)
>
> regards,
>
> François
> fpapon@apache.org <ma...@apache.org>
>
> Le 21/09/2020 à 21:05, Romain Manni-Bucau a écrit :
>> Up, any issue to create a geronimo-stack (happy to get a better
>> name) project?
>>
>>
>> Le lun. 10 août 2020 à 08:47, Romain Manni-Bucau
>> <rmannibucau@gmail.com <ma...@gmail.com>> a écrit :
>>
>> Small up, guess it is still holidays so will wait for a few
>> more weeks to try to get more feedbacks before doing anything.
>>
>> Romain Manni-Bucau
>> @rmannibucau <https://twitter.com/rmannibucau> | Blog
>> <https://rmannibucau.metawerx.net/> | Old Blog
>> <http://rmannibucau.wordpress.com> | Github
>> <https://github.com/rmannibucau> | LinkedIn
>> <https://www.linkedin.com/in/rmannibucau> | Book
>> <https://www.packtpub.com/application-development/java-ee-8-high-performance>
>>
>>
>> Le ven. 31 juil. 2020 à 09:16, Romain Manni-Bucau
>> <rmannibucau@gmail.com <ma...@gmail.com>> a écrit :
>>
>> Makes sense, thanks François
>>
>> Romain Manni-Bucau
>> @rmannibucau <https://twitter.com/rmannibucau> | Blog
>> <https://rmannibucau.metawerx.net/> | Old Blog
>> <http://rmannibucau.wordpress.com> | Github
>> <https://github.com/rmannibucau> | LinkedIn
>> <https://www.linkedin.com/in/rmannibucau> | Book
>> <https://www.packtpub.com/application-development/java-ee-8-high-performance>
>>
>>
>> Le ven. 31 juil. 2020 à 09:15, Francois Papon
>> <francois.papon@openobject.fr
>> <ma...@openobject.fr>> a écrit :
>>
>> Hi Romain,
>>
>> I think the config spec is interesting and could be
>> add to the list.
>>
>> regards,
>>
>> François
>> fpapon@apache.org <ma...@apache.org>
>>
>> Le 31/07/2020 à 08:34, Romain Manni-Bucau a écrit :
>>> Hi everyone,
>>>
>>> After some years of MP I think it is not a safe
>>> enough technology for long term applications - i.e.
>>> maintained and evolved, not just developed for 6 months.
>>> The main drawback is that it changes and breaks too
>>> often and from my understanding it is not likely
>>> about to change (what I understood is it will likely
>>> be worse and can even import vendor/library API in
>>> the spec API as it had been done for tracing one).
>>>
>>> The most common requirements are, IMHO:
>>>
>>> 1. health
>>> 2. metrics (gauge+counter+openmetrics exporter,
>>> others are fancy things)
>>> 3. tracing
>>>
>>> maybe jwt-auth even if less sure.
>>>
>>> Therefore I wonder if we want to fork our own MP
>>> impl to provide these 3 specs simplified versions
>>> with a stable API.
>>> I envision a single repo with the 3 api/impl.
>>>
>>> wdyt?
>>>
>>> Romain Manni-Bucau
>>> @rmannibucau <https://twitter.com/rmannibucau> |
>>> Blog <https://rmannibucau.metawerx.net/> | Old Blog
>>> <http://rmannibucau.wordpress.com> | Github
>>> <https://github.com/rmannibucau> | LinkedIn
>>> <https://www.linkedin.com/in/rmannibucau> | Book
>>> <https://www.packtpub.com/application-development/java-ee-8-high-performance>
>>
Re: Fork some of our MP impls
Posted by Romain Manni-Bucau <rm...@gmail.com>.
Hmm, both are not linked this way (more the opposite ;)).
Why not kat (cat for kubernetes, read somewhere everybody loves cats)? ;)
Btw i dont care much of the name while it can last but Id like some other
opinion if possible (even negative) - otherwise it can be done at github ;).
Le mar. 22 sept. 2020 à 19:34, Francois Papon <fr...@openobject.fr>
a écrit :
> May be we can call it "excalibur" as we already have "arthur" :)
>
> regards,
>
> Françoisfpapon@apache.org
>
> Le 21/09/2020 à 21:05, Romain Manni-Bucau a écrit :
>
> Up, any issue to create a geronimo-stack (happy to get a better name)
> project?
>
>
> Le lun. 10 août 2020 à 08:47, Romain Manni-Bucau <rm...@gmail.com>
> a écrit :
>
>> Small up, guess it is still holidays so will wait for a few more weeks to
>> try to get more feedbacks before doing anything.
>>
>> Romain Manni-Bucau
>> @rmannibucau <https://twitter.com/rmannibucau> | Blog
>> <https://rmannibucau.metawerx.net/> | Old Blog
>> <http://rmannibucau.wordpress.com> | Github
>> <https://github.com/rmannibucau> | LinkedIn
>> <https://www.linkedin.com/in/rmannibucau> | Book
>> <https://www.packtpub.com/application-development/java-ee-8-high-performance>
>>
>>
>> Le ven. 31 juil. 2020 à 09:16, Romain Manni-Bucau <rm...@gmail.com>
>> a écrit :
>>
>>> Makes sense, thanks François
>>>
>>> Romain Manni-Bucau
>>> @rmannibucau <https://twitter.com/rmannibucau> | Blog
>>> <https://rmannibucau.metawerx.net/> | Old Blog
>>> <http://rmannibucau.wordpress.com> | Github
>>> <https://github.com/rmannibucau> | LinkedIn
>>> <https://www.linkedin.com/in/rmannibucau> | Book
>>> <https://www.packtpub.com/application-development/java-ee-8-high-performance>
>>>
>>>
>>> Le ven. 31 juil. 2020 à 09:15, Francois Papon <
>>> francois.papon@openobject.fr> a écrit :
>>>
>>>> Hi Romain,
>>>>
>>>> I think the config spec is interesting and could be add to the list.
>>>>
>>>> regards,
>>>>
>>>> Françoisfpapon@apache.org
>>>>
>>>> Le 31/07/2020 à 08:34, Romain Manni-Bucau a écrit :
>>>>
>>>> Hi everyone,
>>>>
>>>> After some years of MP I think it is not a safe enough technology for
>>>> long term applications - i.e. maintained and evolved, not just
>>>> developed for 6 months.
>>>> The main drawback is that it changes and breaks too often and from my
>>>> understanding it is not likely about to change (what I understood is it
>>>> will likely be worse and can even import vendor/library API in the spec API
>>>> as it had been done for tracing one).
>>>>
>>>> The most common requirements are, IMHO:
>>>>
>>>> 1. health
>>>> 2. metrics (gauge+counter+openmetrics exporter, others are fancy things)
>>>> 3. tracing
>>>>
>>>> maybe jwt-auth even if less sure.
>>>>
>>>> Therefore I wonder if we want to fork our own MP impl to provide these
>>>> 3 specs simplified versions with a stable API.
>>>> I envision a single repo with the 3 api/impl.
>>>>
>>>> wdyt?
>>>>
>>>> Romain Manni-Bucau
>>>> @rmannibucau <https://twitter.com/rmannibucau> | Blog
>>>> <https://rmannibucau.metawerx.net/> | Old Blog
>>>> <http://rmannibucau.wordpress.com> | Github
>>>> <https://github.com/rmannibucau> | LinkedIn
>>>> <https://www.linkedin.com/in/rmannibucau> | Book
>>>> <https://www.packtpub.com/application-development/java-ee-8-high-performance>
>>>>
>>>>
Re: Fork some of our MP impls
Posted by Francois Papon <fr...@openobject.fr>.
May be we can call it "excalibur" as we already have "arthur" :)
regards,
François
fpapon@apache.org
Le 21/09/2020 à 21:05, Romain Manni-Bucau a écrit :
> Up, any issue to create a geronimo-stack (happy to get a better name)
> project?
>
>
> Le lun. 10 août 2020 à 08:47, Romain Manni-Bucau
> <rmannibucau@gmail.com <ma...@gmail.com>> a écrit :
>
> Small up, guess it is still holidays so will wait for a few more
> weeks to try to get more feedbacks before doing anything.
>
> Romain Manni-Bucau
> @rmannibucau <https://twitter.com/rmannibucau> | Blog
> <https://rmannibucau.metawerx.net/> | Old Blog
> <http://rmannibucau.wordpress.com> | Github
> <https://github.com/rmannibucau> | LinkedIn
> <https://www.linkedin.com/in/rmannibucau> | Book
> <https://www.packtpub.com/application-development/java-ee-8-high-performance>
>
>
> Le ven. 31 juil. 2020 à 09:16, Romain Manni-Bucau
> <rmannibucau@gmail.com <ma...@gmail.com>> a écrit :
>
> Makes sense, thanks François
>
> Romain Manni-Bucau
> @rmannibucau <https://twitter.com/rmannibucau> | Blog
> <https://rmannibucau.metawerx.net/> | Old Blog
> <http://rmannibucau.wordpress.com> | Github
> <https://github.com/rmannibucau> | LinkedIn
> <https://www.linkedin.com/in/rmannibucau> | Book
> <https://www.packtpub.com/application-development/java-ee-8-high-performance>
>
>
> Le ven. 31 juil. 2020 à 09:15, Francois Papon
> <francois.papon@openobject.fr
> <ma...@openobject.fr>> a écrit :
>
> Hi Romain,
>
> I think the config spec is interesting and could be add to
> the list.
>
> regards,
>
> François
> fpapon@apache.org <ma...@apache.org>
>
> Le 31/07/2020 à 08:34, Romain Manni-Bucau a écrit :
>> Hi everyone,
>>
>> After some years of MP I think it is not a safe enough
>> technology for long term applications - i.e. maintained
>> and evolved, not just developed for 6 months.
>> The main drawback is that it changes and breaks too often
>> and from my understanding it is not likely about to
>> change (what I understood is it will likely be worse and
>> can even import vendor/library API in the spec API as it
>> had been done for tracing one).
>>
>> The most common requirements are, IMHO:
>>
>> 1. health
>> 2. metrics (gauge+counter+openmetrics exporter, others
>> are fancy things)
>> 3. tracing
>>
>> maybe jwt-auth even if less sure.
>>
>> Therefore I wonder if we want to fork our own MP impl to
>> provide these 3 specs simplified versions with a stable API.
>> I envision a single repo with the 3 api/impl.
>>
>> wdyt?
>>
>> Romain Manni-Bucau
>> @rmannibucau <https://twitter.com/rmannibucau> | Blog
>> <https://rmannibucau.metawerx.net/> | Old Blog
>> <http://rmannibucau.wordpress.com> | Github
>> <https://github.com/rmannibucau> | LinkedIn
>> <https://www.linkedin.com/in/rmannibucau> | Book
>> <https://www.packtpub.com/application-development/java-ee-8-high-performance>
>
Re: Fork some of our MP impls
Posted by Romain Manni-Bucau <rm...@gmail.com>.
Up, any issue to create a geronimo-stack (happy to get a better name)
project?
Le lun. 10 août 2020 à 08:47, Romain Manni-Bucau <rm...@gmail.com> a
écrit :
> Small up, guess it is still holidays so will wait for a few more weeks to
> try to get more feedbacks before doing anything.
>
> Romain Manni-Bucau
> @rmannibucau <https://twitter.com/rmannibucau> | Blog
> <https://rmannibucau.metawerx.net/> | Old Blog
> <http://rmannibucau.wordpress.com> | Github
> <https://github.com/rmannibucau> | LinkedIn
> <https://www.linkedin.com/in/rmannibucau> | Book
> <https://www.packtpub.com/application-development/java-ee-8-high-performance>
>
>
> Le ven. 31 juil. 2020 à 09:16, Romain Manni-Bucau <rm...@gmail.com>
> a écrit :
>
>> Makes sense, thanks François
>>
>> Romain Manni-Bucau
>> @rmannibucau <https://twitter.com/rmannibucau> | Blog
>> <https://rmannibucau.metawerx.net/> | Old Blog
>> <http://rmannibucau.wordpress.com> | Github
>> <https://github.com/rmannibucau> | LinkedIn
>> <https://www.linkedin.com/in/rmannibucau> | Book
>> <https://www.packtpub.com/application-development/java-ee-8-high-performance>
>>
>>
>> Le ven. 31 juil. 2020 à 09:15, Francois Papon <
>> francois.papon@openobject.fr> a écrit :
>>
>>> Hi Romain,
>>>
>>> I think the config spec is interesting and could be add to the list.
>>>
>>> regards,
>>>
>>> Françoisfpapon@apache.org
>>>
>>> Le 31/07/2020 à 08:34, Romain Manni-Bucau a écrit :
>>>
>>> Hi everyone,
>>>
>>> After some years of MP I think it is not a safe enough technology for
>>> long term applications - i.e. maintained and evolved, not just
>>> developed for 6 months.
>>> The main drawback is that it changes and breaks too often and from my
>>> understanding it is not likely about to change (what I understood is it
>>> will likely be worse and can even import vendor/library API in the spec API
>>> as it had been done for tracing one).
>>>
>>> The most common requirements are, IMHO:
>>>
>>> 1. health
>>> 2. metrics (gauge+counter+openmetrics exporter, others are fancy things)
>>> 3. tracing
>>>
>>> maybe jwt-auth even if less sure.
>>>
>>> Therefore I wonder if we want to fork our own MP impl to provide these 3
>>> specs simplified versions with a stable API.
>>> I envision a single repo with the 3 api/impl.
>>>
>>> wdyt?
>>>
>>> Romain Manni-Bucau
>>> @rmannibucau <https://twitter.com/rmannibucau> | Blog
>>> <https://rmannibucau.metawerx.net/> | Old Blog
>>> <http://rmannibucau.wordpress.com> | Github
>>> <https://github.com/rmannibucau> | LinkedIn
>>> <https://www.linkedin.com/in/rmannibucau> | Book
>>> <https://www.packtpub.com/application-development/java-ee-8-high-performance>
>>>
>>>