+0 for me.

Again, it’s interesting, a blueprint/tutorial is possible but I would go with 
something more concrete.

It’s what I started while ago with Karaf-boot and now on Karaf DevX branch.

Go ahead if you want but my concerns are:

- it will be maybe too abstract and complex for non OSGi users (spring-boot 
guys especially)
- as I follow agree with your view about "too much fine grained services" (it’s 
something that I discussed with Netflix), I think a runtime would be welcome

So, I’m no against, but I think the DevX approach is more concrete, straight, 
and addressing non OSGi users.

Regards
JB

> Le 15 avr. 2020 à 07:15, Christian Schneider <[email protected]> a 
> écrit :
> 
> (I first proposed this in felix. Some people hinted that Aries might be a
> better fit. So I am also starting this discussion here)
> 
> In recent years we saw a big trend towards micro services and cloud.
> Lately people discovered though that such services are often made too fine
> grained.
> The newest trend goes to building bigger micro services on the level of
> domain driven design bounded contexts.
> 
> Especially for these services OSGi is a very interesting platform as they
> need more internal structure than the more fine grained services.
> Unfortunately it is quite hard to build a cloud native service in OSGi from
> scratch.
> 
> So I would like to offer a blueprint for cloud native micro services inside
> the felix community. The goal is to provide all parts of a cloud native
> system that are usually needed, like:
> 
> * Declarative services as dependency injection
> * Aries Jaxrs Whiteboard for REST
> * Dropwizard metrics exported as Prometheus metrics
> * Swagger
> * Halbrowser
> * Felix healthchecks
> * Configuration using OSGi configurator + Environment variables plugin
> * Logging to console
> * Final application is provided as a runnable jar
> * Example docker build files
> * Example kubernetes yaml
> 
> What do you think?
> 
> Christian
> 
> -- 
> -- 
> Christian Schneider
> http://www.liquid-reality.de
> 
> Computer Scientist
> http://www.adobe.com

Reply via email to