Uses of Record Class
com.eqixiac.equinix.design.spi.MetroPortfolio

Packages that use MetroPortfolio
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.
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.
Portfolio search: the reference ExhaustiveSolver, the Pareto dominance rules it uses, and the named WeightProfiles that turn a spec's objectives into weights.
Extension points of the design engines.
Sustainability plug-ins for the design engines.
The value-realization layer of the design API: design-time cost modelling that puts a money figure on an interconnect decision.
Cloud-egress savings estimation: how much routing a monthly data volume over an Equinix private interconnect saves versus egressing it to the public internet, net of the Equinix interconnect cost.
Design-time total-cost-of-ownership comparison across the DeploymentArchetypes - public cloud over the internet, on-premises, Equinix-interconnected, and (for a cloud-to-cloud comparison) the providers' native multicloud link.