Creating Self-Balancing Solutions with Solaris Containers

compared with
Current by Elena_Levashova
on Oct 20, 2008 18:54.

Key
This line was removed.
This word was removed. This word was added.
This line was added.

Changes (4)

View page history
h4.[Creating Self-Balancing Solutions with Solaris Containers !Main^download.gif!|http://www.sun.com/blueprints/0605/819-2888.pdf]
*by David Collier-Brown*
{excerpt}June, 2005{excerpt}
 
 
Transactions of some kind are an integral part of every organization, and must be completed on time if the business is to operate effectively and efficiently. Chaos, and damage, can be caused if critical transactions are not handled correctly. Today, IT managers often try to break workloads into chunks and process them with separate program instances in the hope that they can distribute the workload across the instances and keep pace with demand. This technique has its drawbacks. What happens when one instance fails to finish in time? Worse, what if the business is growing, and every month the number of lagging instances increases? How are system administrators supposed to figure out which instance is going to be late the next time?

The individuals who post here are part of the extended Sun Microsystems community and they might not be employed or in any way formally affiliated with Sun Microsystems. The opinions expressed here are their own, are not necessarily reviewed in advance by anyone but the individual authors, and neither Sun nor any other party necessarily agrees with them.

Copyright 1994-2009 Sun Microsystems, Inc.
Powered by Atlassian Confluence
Sun Guidelines on Public Discourse Privacy Policy Terms of Use Trademarks Site Map Employment Investor Relations Contact