Home
Downloads
 
Products
So what's the idea with these pictures?
 
Useful links
How ready is OSGi to be used for real enterprise app dev? How does OSGi address the lack of versioning of Java classes and modularity in the context of classpath hell.
InfoQ: Ever since the OpenSOA initiative published the white paper entitled: "Power Combination, SCA, OSGi and Spring", the combination of these three technologies has generated some interest ...
Java.net: Introduce SCA and show how it can be used for building standards-based enterprise class apps ...
InformationWeek: OSGi has the potential to change the deployment model for enterprise applications ...
Pipeline: The next generation of distributed software system ...
Artima Developer: Leading-Edge Java: Polite and Impolite Services ...
DavidChappell: This overview provides an architectural intro to SCA ...
SYS-CON.TV: Paremus CEO discusses his vision for distributed SOA ...
Ubiquity: The best way to fight complexity is to strive for IT simplicity ...
SD Times: OSGi ... the most important technology of the decade!?
GRIDToday: Survey highlights risks of infrastructure complexity.
SAIC: Defense consortium uses Infiniflow for dynamic Semantic SOA.
 
 
 
Business Solutions
 
How can I improve resource utilization and service availability at lower cost?  
Operations solutions ...
Technical answers ...
         
 
  Data centers are under unprecedented pressure from a combination of space, power and cooling constraints, yet the servers they contain typically achieve only 15% to 20% utilization. Clearly an improvement in compute resource utilization will deliver significant cost benefit and competitive advantage to most organizations.
   
 

The global 24 x 7, always-on economy means that application availability is demanded by customers, partners and the markets. This has lead to the traditional, inefficient approach of high availability, N+1, solutions and the implementation of dedicated resources to cater for peak computing requirements, both of which compound the resource under-utilization dilemma and stretch data center budgets even further.

   
 

So wouldn't it be great if you could dynamically scale your applications, allowing the busy ones to use under-utilized resources, and spread critical services over many servers to reduce the risk of downtime?

   
 

The main technical obstacle has been the way in which monolithic applications are allocated to servers in 'stove-pipes' or 'silos'. By abstracting the applications from the underlying hardware, Infiniflow allows you to free your applications from the existing stove-pipes and run them across any of your available compute resources, automatically scaling up, scaling down and adjusting them to meet SLA's and respond to changes in the resource landscape.

No longer do servers sit there waiting for their scheduled task, warming the data center for no return. Instead they are automatically and dynamically configured and reconfigured to run different applications throughout the day.

Service availability is traditionally improved by trying to stop things from breaking using duplicated 'hot standby' resources. While this approach has achieved a degree of success, it is inefficient and expensive as ultimately failure can not be avoided.

Managing your data center can become like plate spinning, where the number of plates is ever increasing and the only way to try to keep them spinning is to buy more poles and employ more people. While today individual failures may go unnoticed, or take significant time to resolve, the occurance of multiple, often seemingly unreleated, cascading failures can result in catastrophic failure¹ that cause extended periods of business critical downtime.

In contrast, Infiniflow maximizes service availability by adopting a recovery oriented approach. By accepting that failure will always happen and not trying to stop the inevitable, Infiniflow distributes your critical business applications and then minimizes the time it takes to recover from failure.

This achieves a much higher level of service availability and provides cost and resource utilization benefits. You can avoid the expense of complex high availability N+1 architectures, and you need fewer people to keep your applications running.

 

 

1

Perrow: Normal Accidents: Living with High Risk Technologies, 1999, ISBN13: 978-0-691-00412-9
 
 
More questions to follow ...
 
 

If you would like to comment on this answer or submit further questions, please send us an email.

   
 
 
 
 
  Quick links
   
 

Infiniflow Evaluation

  Industries & Use Cases
  Technology & Standards
  Training
  ECM
  Blogs
  Careers
  Contact us
  P: (USA) +1 646-202-2920
  P: (EMEA) +44 207 936 9098
  E: info@paremus.com
 
 
 
 
 
Terms of Use and Privacy Policy
Infiniflow is a trademark of Paremus Ltd. All rights reserved.
Copyright © Paremus Ltd 2001-2007