Uses of Package
com.eqixiac.equinix.design.resilience
Packages that use com.eqixiac.equinix.design.resilience
Package
Description
Root package for the Equinix Java SDK.
The Design Decision Record: the one document an architect hands to a review board for a
DesignSpec.Failure analysis of a design.
-
Classes in com.eqixiac.equinix.design.resilience used by com.eqixiac.equinixClassDescriptionAnalyses how a design survives failures: builds its
DesignGraph, simulates every single failure (exhaustively) and pairs of failures (bounded), ranks the blast radius, finds single points of failure and correlated risks, estimates availability and proposes remediation, re-simulating it where it can. -
Classes in com.eqixiac.equinix.design.resilience used by com.eqixiac.equinix.design.recordClassDescriptionHow a design graph is built and simulated.The resilience analysis of one design: its graph, what every failure scenario leaves working, the blast-radius ranking, single points of failure, correlated risks, N-1 and N-2 verdicts, estimated availability and remediation.
-
Classes in com.eqixiac.equinix.design.resilience used by com.eqixiac.equinix.design.resilienceClassDescriptionThe availability assumed for each kind of element, as a fraction (0.9995 = 99.95%).An explicit, immutable graph of one design: sites, metros, Cloud Routers, cloud on-ramps, clouds, workloads and (optionally) peer networks, joined by access circuits, the inter-metro backbone, primary and standby cloud connections, provider links and workload hosting, each with its capacity and round-trip latency where known.What a
GraphEdgeof aDesignGraphstands for.Whether a redundant edge is the one used in normal operation or the one held for failover.The kinds of element an availability is assumed for (seeAvailabilityAssumptions).One failure to simulate: the graph nodes and edges it takes away.One edge of aDesignGraph.One node of aDesignGraph.How much of a portfolio's baseline service survives its worst single-element failure, measured by simulation: the shared core ofSimulatedResilienceObjectiveandMinSurvivalConstraint.What aGraphNodeof aDesignGraphstands for.Where a peer network is present, for drawing it into aDesignGraph.A workload as the graph sees it: where it runs, where it fails over to and what it needs.Analyses how a design survives failures: builds itsDesignGraph, simulates every single failure (exhaustively) and pairs of failures (bounded), ranks the blast radius, finds single points of failure and correlated risks, estimates availability and proposes remediation, re-simulating it where it can.Two (or more) elements that are meant to back each other up but share a failure domain.An N-1 or N-2 verdict level.The N-1 or N-2 verdict.What the pairwise (N-2) simulation covered.One scenario in the blast-radius ranking (worst first).A concrete change and the scenarios it addresses.How serious a correlated risk is.A single element whose failure causes an outage.How a design graph is built and simulated.The resilience analysis of one design: its graph, what every failure scenario leaves working, the blast-radius ranking, single points of failure, correlated risks, N-1 and N-2 verdicts, estimated availability and remediation.The pairwise scenarios and how many exist.What aFailureScenariotakes away.What still works in one scenario, compared with the baseline.The outcome of one scenario, compared with the baseline (no failure).The estimated availability of one workload, composed fromAvailabilityAssumptionsover the graph's redundant paths.What happens to one workload in one scenario.How one workload fares in a scenario.