Re: [jakartaee-spec-project-leads] Jakarta NoSQL and Eclipse MicroProfil

[Emily Jiang <emijiang6@xxxxxxxxxxxxxx>]

Hi Otavio,

As promised via our chat, I would share my view here.

I totally agree that Configuration is very important for developing cloud-native microservices. It is a best practice in 12-Factor App to make microservice configurable. MicroProfile Config exists for exactly that reason. I strongly recommend to use it.

As for your question of whether it is ok for Jakarta EE to depend on Eclipse MicroProfile Config, I think it is a good idea. Since many people including Adam Bien, myself, etc, seriously think Jakarta EE + MicroProfile are very powerful together and most of time they are needed at the same time, I strongly think it makes sense for Jakarta EE specs also utlising MicroProfile specs such as MicroProfile Config, etc. MicroProfile specs already pull in Jakarta EE specs, such as CDI, JAX-RS, JSON-B and JSON-P. Technically Jakarta EE should be able to pull in MicroProfile specs.

If a lightweight onboarding process is needed to enable MicroProfile specs to be used in Jakarta Specs, I am ok with that. It is very important that MicroProfile and Jakarta continue complementing with each other not competing with each other.

My 2cents.

Emily

On Sun, Sep 15, 2019 at 9:07 PM Otavio Santana <otaviopolianasantana@xxxxxxxxx> wrote:

Hello everyone, I have one question about the integration between Jakarta and Eclipse MicroProfile.
As you know, Jakarta EE has the goal of the cloud-native application, so we tend to use good practices on that.
There is the twelve-factor of an App that has the good practices of delivery your application in the cloud, and the third item there is the configuration.

My whole point here is that need to have one API to all Jakarta EE project to use related to configuration. We might use this API on several projects such as JPA, JMS, and so on. Right now, we're facing this discussion on Jakarta NoSQL.

My question is: Do we have plans to integrate Jakarta EE with Eclipse MicroProfile Configuration?
I'm not happy with a copy/paste approach from a feature that already exists, because that means two points to maintain; furthermore, that is not good code practices.

In the cloud, the perspective configuration will be like CDI, because several specifications are going to use it. Right now, my best shot to Jakarta NoSQL is to use only in the Reference implementation and put it as optional.

--

Otávio Santana

twitter: http://twitter.com/otaviojava

site:     http://about.me/otaviojava

_______________________________________________
jakartaee-spec-project-leads mailing list
jakartaee-spec-project-leads@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/jakartaee-spec-project-leads

--

Thanks
Emily
=================
Emily Jiang
ejiang@xxxxxxxxxx