Looking forward to what you come up with. Do you already have something to look into or help with?
I will try to get along without a special runtime (basically just felix framework + suitably configured bundles). For a first application assembly I plan to use bnd maven plugins like in the enroute example. There is a lot of possible space for improvements though. I hope there are some cool tools from karaf we can use to make the assembly and runtime even better. Christian Am So., 12. Apr. 2020 um 19:46 Uhr schrieb Jean-Baptiste Onofre < j...@nanthrax.net>: > Hi Christian, > > That’s interesting, but I think that people are expecting more than that. > > 1. Most of the time, we do things too much complex. > 2. Assembly again layers is not always easy > 3. Where’s the runtime ? > > Your main point is valid: lot of people went too far in fine grained > services and now, they are thinking about "smart" micro services. > That’s exactly the purpose of Netflix using Apache Karaf. > > Back on your point, that’s the target of "new" Karaf tool that I restarted > (re-starting/founding Karaf Boot we discussed while ago that addressed > exactly the points you mentioned). > > So, why not having a blueprint (I still think people wants to create their > own blueprint), but having tool + runtime is more interesting and that’s > why I’m working on Karaf "DevX code" PoC. > > Regards > JB > > > Le 12 avr. 2020 à 11:58, Christian Schneider <ch...@die-schneider.net> > a écrit : > > > > 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 > > -- -- Christian Schneider http://www.liquid-reality.de Computer Scientist http://www.adobe.com
