IMG_0002
The use of OSGi technology has evolved over the past decade from being used to manage devices (service gateways etc.), to providing an extensible framework for desktop applications (Eclipse RCP), to being used by a majority of JEE servers for implementing extensible and modular servers, and as a programming model for developing server-side applications as well as applications deployed to the cloud. When deploying OSGi applications to the cloud the cost of the infrastructure that is required to run the application vs the isolation needs of each individual application must be taken into account.
Various architectures are available that range from no-sharing to shared multitenant. With no-sharing each OSGi Application uses its own JVM and OSGi Framework instances in order to run the application. This provides nice isolation for each application but adds additional overhead for each application deployed. Other application models exist, such as OSGi subsystems, that allow applications to share the same JVM and OSGi framework instance to host multiple applications. While this model can provide optimal sharing, it comes at the cost of significantly reducing isolation for each application deployed to the shared OSGi Framework.
IMG_0002
The use of OSGi technology has evolved over the past decade from being used to manage devices (service gateways etc.), to providing an extensible framework for desktop applications (Eclipse RCP), to being used by a majority of JEE servers for implementing extensible and modular servers, and as a programming model for developing server-side applications as well as applications deployed to the cloud. When deploying OSGi applications to the cloud the cost of the infrastructure that is required to run the application vs the isolation needs of each individual application must be taken into account.
Various architectures are available that range from no-sharing to shared multitenant. With no-sharing each OSGi Application uses its own JVM and OSGi Framework instances in order to run the application. This provides nice isolation for each application but adds additional overhead for each application deployed. Other application models exist, such as OSGi subsystems, that allow applications to share the same JVM and OSGi framework instance to host multiple applications. While this model can provide optimal sharing, it comes at the cost of significantly reducing isolation for each application deployed to the shared OSGi Framework.