Abstract: A system associated with a distributed cloud service may include an active network node within a network environment between a provider application and a consumer application. The active network node may have an execution environment, an operating system to support the execution environment, and active hardware. The active network node may automatically detect, via a platform and language independent centralized resilience process, a failure event in an active network that routes packets to support the distributed cloud service. The failure event might be associated with, for example, an unreliable network, a low bandwidth, a high latency, a topology change, transport costs, etc. Responsive to the detection of the failure event, the active network node may dynamically implement an application resilience pattern (e.g., a circuit breaker or bounded queue) by the centralized resilience process to facilitate recovery from the detected failure event without participation of the consumer application.

Abstract: A cloud computing design evaluation platform may receive a master variant for a cloud computing design, including a sequential sequence of a set of components. The evaluation platform may then determine a maximum number of parallel levels for the master variant and automatically create a plurality of potential variants of the master variant by expanding the master variant with parallel components in accordance with the maximum number of parallel levels. The evaluation platform determines reliability information (e.g., based on MTBF data) and cost information (e.g., a TCO) for each component. An overall reliability score and overall cost score for each of the automatically created potential variants is automatically calculated and an evaluation result of the calculation is indicated (reflecting an optimum design that meets SLA and TCO goals). Some embodiments may also provide continuous monitoring of design performance and/or predict future design performance based on historical data.

Abstract: A system associated with a distributed cloud service may include an active network node within a network environment between a provider application and a consumer application. The active network node may have an execution environment, an operating system to support the execution environment, and active hardware. The active network node may automatically detect, via a platform and language independent centralized resilience process, a failure event in an active network that routes packets to support the distributed cloud service. The failure event might be associated with, for example, an unreliable network, a low bandwidth, a high latency, a topology change, transport costs, etc. Responsive to the detection of the failure event, the active network node may dynamically implement an application resilience pattern (e.g., a circuit breaker or bounded queue) by the centralized resilience process to facilitate recovery from the detected failure event without participation of the consumer application.