With OSGi's JAX-RS support [1], you can easily publish and consume RESTy endpoints in your OSGi application.
So there is no need to "leave" OSGi to participate in a microservice environment.
--
BJ Hargrave
Senior Technical Staff Member, IBM // office: +1 386 848 1781
OSGi Fellow and CTO of the OSGi Alliance // mobile: +1 386 848 3788
[email protected]
BJ Hargrave
Senior Technical Staff Member, IBM // office: +1 386 848 1781
OSGi Fellow and CTO of the OSGi Alliance // mobile: +1 386 848 3788
[email protected]
----- Original message -----
From: Neil Bartlett via osgi-dev <[email protected]>
Sent by: [email protected]
To: Mohamed AFIF <[email protected]>, OSGi Developer Mail List <[email protected]>
Cc:
Subject: Re: [osgi-dev] Migrating from OSGI to Microservices
Date: Thu, May 2, 2019 6:37 AM
Well the good news is that OSGi is already a microservice architecture, so you have already finished. Congratulations!If that answer doesn't quite satisfy you, maybe you'd like to describe in more detail what you are attempting to achieve and why?Regards,NeilOn Thu, 2 May 2019 at 11:06, Mohamed AFIF via osgi-dev <[email protected]> wrote:Hello everybody,_______________________________________________We 're starting to study the possibility to transform our architcteure in order to migrate from OSGI to microservice architecture, and I would like to know if there is alreay some people who had thought about this subject or already start this migration.Because at first sight it would not be an easy task, many problems/issues we will be facing to them (blueprint injections, managing ditrubued caches instead of one cache in one JVM...)Many thanks--CdtMohamed AFIF
OSGi Developer Mail List
[email protected]
https://mail.osgi.org/mailman/listinfo/osgi-dev_______________________________________________
OSGi Developer Mail List
[email protected]
https://mail.osgi.org/mailman/listinfo/osgi-dev
_______________________________________________ OSGi Developer Mail List [email protected] https://mail.osgi.org/mailman/listinfo/osgi-dev
