Uses of Interface
com.eqixiac.equinix.design.spi.DesignContext

Packages that use DesignContext
Package
Description
The built-in hard limits of the Metro Optimizer: one small, pure Constraint per field of DesignConstraints, plus the workload rules, the single-currency budget and the every-metro-used rule.
Pricing of candidate designs: RateCardCostModel is the CostModel the Metro Optimizer uses, pricing each metro's needs from a RateCard with every line's source and a range from PriceBands.
The built-in objectives of the Metro Optimizer: latency, cost, provider coverage, resilience and compliance.
The facts of a Metro Optimizer run: CatalogDesignContext (an in-memory DesignContext with a builder), FabricCatalogLoader (builds one from live Fabric data, read-only) and ProviderCatalog (which metros each cloud is reachable from).
Workload placement on a chosen set of metros: WorkloadPlacer decides where each workload runs (honouring pinnedMetro, per-workload maxLatencyMs and cloud reachability) and which cloud connections that implies, as a PlacementPlan.
Failure analysis of a design.
Extension points of the design engines.
Sustainability plug-ins for the design engines.