The Paremus Service Fabric can be used for a single application on a small cluster through to multiple different applications across entire data centers, dynamically moving the Cloud compute resources between applications according to real-time business demands, pre-defined SLA’s and resource availability.

Applicability of the Service Fabric is cross industry and customers are typically driven by a desire to meet one or all of the following:

• reduce operational and capital costs
• increase business agility
• improve productivity
• gain competitive advantage

Industries in which the Service Fabric is being used include Defense, Finance and Web2.0/3.0.

The Service Fabric is middleware and protocol agnostic, allowing you to select the most appropriate functionality for each specific application. Paremus offers an evolving library of packaged Runtime Patterns that come pre-integrated with middleware and messaging to deliver ‘out-of-the-box’ solutions to meet specific business processing requirements.

With transparent support for WARs, POJOs, Spring Framework, Peaberry (Guice) t is easy to take an existing Java application, or write a new one, and add dynamic scale and resilience to it by deploying it on the Paremus Service Fabric.  Applications not in Java, no problem, the Service Fabric can support non-Java applications too.

It couldn’t be any easier. The Service Fabric’s WAR support removes the need for administrative intervention to set-up and remove correctly configured Servlet Engines each time you want to deploy or remove a Web Application.

All you have to do is specify the WAR file containing your application and the Service Fabric will automatically install all the necessary supporting infrastructure. When you're finished with the Web Application the Service Fabric will, assuming nothing else is using it, tear down all of this supporting infrastructure, completing the Web Application lifecycle.

The Paremus Service Fabric provides transparent support for both the ‘classic’ Spring, i.e. the original POJO framework and also the more recent OSGi-based SpringDM framework allowing you to easily add resilience, scale and dynamicity to your applications based on these two frameworks.  For more information on how easy it is to run your Spring-based apps on the Service Fabric you should check out the webinar on this topic.

The Peaberry project provides the OSGi enablement of the Google Guice framework. Any applications built using Peaberry can benefit from the Service Fabric in exactly the same way as those written with the Spring Framework.

Please see Use Cases for some examples of the Paremus Service Fabric in action.