Forgot the link. The current state can be viewed in https://github.com/cschneider/osgi-best-practices
It already implements most of the aspects above but still got some rough edges. The example also contains some bundles like the swagger and halbrowser repackagings that should rather be versioned separately so users of the example can simply reference them. Christian Am Mi., 15. Apr. 2020 um 07:15 Uhr schrieb Christian Schneider < [email protected]>: > (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 > > -- -- Christian Schneider http://www.liquid-reality.de Computer Scientist http://www.adobe.com
