Paremus Service Fabric

Paremus Service Fabric Features & Benefits

The Paremus Service Fabric features offer a number of technical and business benefits including:

Feature	Technical Benefit	Business Benefit
Private Cloud	Hardware and Operating System agnostic, the Service Fabric is able to run across any available data center compute resources, both physical and virtual. This enables organizations to turn their da ctaenters in to their own secure Private Clouds.	Underutilized resources can be put to better use and new server purchase decisions can be based just on price, performance and form factor metrics. Technology refresh becomes a run of the mill, business as usual activity, rather than a major high risk project.
Highly Automated and Dynamic	Applications and the runtime automatically respond to changes in the environment, minimizing the level of human intervention required to provision, operate and remove applications. The applications and Service Fabric runtime: Self-assemble Self-heal Self-manage Self-scale Self-audit	Automation provides huge OPEX cost savings by simplifying the day-to-day management of the IT systems and datacenter environments. Applications and their runtime are no longer change resistant and brittle making it easier to accommodate changing business and customer requirements and maximize service availability.
Model-Driven	Each application and its runtime behavior is described and managed by a Model. Once a System Model is 'activated' the compute resources in the Service Fabric (physical and virtual) respond to capability requests and build themselves to deliver the functionality described in the model.	Business agility is enabled by a flexible, adaptive runtime. Implementation and upgrades are no longer labor intensive, hugely disruptive or costly.
Standards-Based	The Paremus Service Fabric is Java-centric and leverages OSGi™ and SCA: OSGi provides a dynamic, component, lifecycle framework for both the Paremus Service Container and also the Applications that on the Service Fabric. SCA provides a protocol, language and runtime neutral application wire-up description structure.	The Paremus Service Fabric utilizes the same standards that all Java application servers are adopting. Enabling applications to support these standards means you avoid vendor lock-in.
Distributed Self-Healing Command and Control	The Paremus Service Fabric has no single point of failure and no special frames of reference. Failure is expected, rather than the exception, so the Service Fabric focuses on minimizing recovery time rather than trying to stop things from breaking.	Application and system availability is proven to be higher when you accept that failure is inevitable and stop spending lots of money trying to stop it from happening.
Dynamic Scale	The application can be dynamically right-sized by the Service Fabric without any need for technical intervention. The Paremus Service Fabric can dynamically scale up and down in response to external metrics such as throughput or number of users of an application.	‘Right-Sizing’ applications means that your compute resource utilization is optimized while ensuring that you provide the necessary service to your users and customers. This saves significant costs compared with the usual approach of over specifying and dedicating hardware stovepipes to each and every application.