Sorry .. seems I forgot the link: https://github.com/cschneider/osgi-best-practices
Am Mo., 13. Apr. 2020 um 16:24 Uhr schrieb Christian Schneider < ch...@die-schneider.net>: > Hi Karl, > > I just updated my osgi best practices example to show what I have in mind. > > It now supports: > - dropwizard metrics as prometheus /metrics > - swagger generation from source > - swagger-ui > - hal-browser > > Just follow the readme and you can see how it looks. > > Christian > > Am So., 12. Apr. 2020 um 23:05 Uhr schrieb Karl Pauls <karlpa...@gmail.com > >: > >> Hi Christian, >> >> I don't think we are at that point just yet. Given that this is a >> holiday surrounded weekend for a lot of us (due to the easter break) I >> would say we should at least give it a couple of more days to see >> where the discussion is going. >> >> That said, I personally would like to see a little bit more about what >> you had in mind. Is there already some existing body of work or are >> you planning to create something from scratch? >> >> regards, >> >> Karl >> >> On Sun, Apr 12, 2020 at 9:32 PM Christian Schneider >> <ch...@die-schneider.net> wrote: >> > >> > There seems to be some interest in having such a blueprint or even more >> > than one variant at felix. >> > >> > Should I start in felix-dev or use a new repo? >> > I would prefer a new repo as the code will be a multi module maven >> project. >> > I propose a repo name "felix-cloud-native-starter". >> > We could have and have different blueprints (e.g. CDI and DS) inside. >> > I thought about but disliked to have "blueprint" in the name as people >> > might confuse it with the blueprint dependency injection. >> > >> > Christian >> > >> > Am So., 12. Apr. 2020 um 11:58 Uhr schrieb Christian Schneider < >> > ch...@die-schneider.net>: >> > >> > > 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 >> >> >> >> -- >> Karl Pauls >> karlpa...@gmail.com >> > > > -- > -- > 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
