Paremus Service Fabric for the Developer

The Developer Perspective

The drivers for OSGi™ adoption are as simple as they are fundamental: to increase business agility and to improve organizational efficiency. Yet modularization, by necessity, results in a new level of structural dependencies being exposed to you, the developer; and these must be effectively managed.

Making OSGi Nimble

Paremus has responded to this ‘dependency challenge’ with Nimble, a policy driven dependency resolution engine and interactive, scriptable OSGi shell. Nimble enables you to simply manage OSGi dependencies, and allows you to rapidly assemble and interact with OSGi-based applications. Lightweight, Simple, Elegant and Powerful, Nimble is a joy to use and pretty much essential if you are developing applications comprising of 10’s, 100’s or even 1000’s of OSGi bundles.

As a general dependency resolver, Nimble also understands runtime and/or environmental dependencies. When presented with a WAR, Nimble understands that this requires a Servlet engine and dynamically installs your preferred Servlet implementation. Presented with an EAR, Nimble responds by creating the appropriate JEE runtime.

Avoid Developer Lock-in!

Neither Nimble nor the Service Fabric (a Cloud of Nimble-enabled compute nodes) constrains your choice of development framework.

Nimble supports all popular Java/OSGi IoC frameworks, including OSGi Blueprint Service, Declarative Services, iPOJO and Guice/Peaberry. In addition to the Java language, Nimble also understands Scala’s runtime requirements, and may be simply extended to support any language that targets the Java JVM.

By supporting WAR and EAR artifacts, Nimble allows for the gradual re-factoring and replacement of existing legacy code with OSGi-based alternatives. Indeed, Nimble and the composite nature of OSGi-based applications also prompt subsequent incremental evolution of applications. For example, an application may initially be comprised of a number of Spring DM components, yet later, developers are able to incrementally migrate components to alternatives such as Declarative Services or Scala.

Develop Locally – Deploy in the Cloud

Pluggable ‘Service Bindings‘ make it simple to develop and test components within a local Nimble container and then distribute these across the Paremus Service Fabric. Sophisticated horizontal scaling behaviors can be applied to each component within your application allowing them to dynamically scale in response to changing business conditions.

The industry’s most advanced private Java™ Cloud runtime, the Paremus Service Fabric provides the agility and scalability your business needs while maintaining your freedom to choose the most appropriate development framework at each point in time!