celix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Pepijn Noltes <pepijnnol...@gmail.com>
Subject Re: Next Celix release
Date Tue, 13 Feb 2018 20:29:55 GMT
Hi Gerrit,

An interesting question.

The issue with mircroservices for a framework like Celix IMO is how to
define and use a (language independent) microservice API  REST/JSON) in
natural way for C, C++ & service oriented

For the microservices API there already a lot of options and I think we
should not reinvent the wheel for this. A big downside is that - as far as
I know - technologies like gRPC,  protobuf, avro, etc generate a lot of
code, but do not generate a clear and pure abstract interfaces as primary
"to use" API .. its al one mess. I personally really dislike this and think
is works against the general idea of OSGi/service oriented (hide your
privates / implementation details).

But I do agree that microsevices - and as result a microservices chassis
frameworks - are an interesting path to look into and can really help move
Celix forward.  Microservices and OSGi/service oriented as techniques
should very compatible.

I am curious if anybody else has any though on this. Or any hints for
certain technology to look at?

Greetings,
Pepijn


On Fri, Feb 9, 2018 at 8:38 AM Gerrit Binnenmars <gerritbinnenmars@gmail.com>
wrote:

> Hello,
>
> To produce some spam :-).
> Celix now includes Remote services and Pub Sub.
> Would it be possible to create a generic solution to invoke remote services
> based on REST and/or gRPC.and expose services using REST and/or gRPC?
>
> Gerrit
>
> On Fri, Feb 9, 2018 at 8:31 AM, Gerrit Binnenmars <
> gerritbinnenmars@gmail.com> wrote:
>
> > Hello Pepijn and others,
> >
> > Could you for the next release have a look at the following page:
> > http://microservices.io/patterns/microservice-chassis.html
> >
> > For me externalized configuration and distributed tracing should be high
> > on the prio list.
> > The config admin is not well usable and for service invocation tracing no
> > facilities are available yet.
> >
> > I like the idea of positioning Celix as an elaborate microservice chassis
> > framework.
> >
> > Greetings Gerrit
> >
> > On Thu, Oct 12, 2017 at 8:46 PM, Pepijn Noltes <pepijnnoltes@gmail.com>
> > wrote:
> >
> >> Hi All,
> >>
> >> In the last weeks we did some considerable work on improving the pubsub
> >> functionality, including pluggable serializers. This is one of the
> feature
> >> I wanted in the next release. Also If I am correct we currently have no
> >> open issues in coverity.
> >> All in all this is IMO a good starting point to create a release.
> >>
> >> What is left todo is creating a release branch, some additional
> >> testing/fixing, ensuring the documentation is up to date, update the
> JIRA
> >> issues and creating a release log.
> >> I will pick this up and hope te be able to start a release vote within 2
> >> weeks.
> >>
> >> Please let me know if there any request/remarks concerning the next
> Celix
> >> release.
> >>
> >> Greetings,
> >> Pepijn
> >>
> >
> >
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message