Package com.eqixiac.equinix.design.optimizer

package com.eqixiac.equinix.design.optimizer

The Metro Optimizer: which set of Equinix metros best serves a DesignSpec, as a multi-objective search.

MetroOptimizer.forSpec(FabricGateway, DesignSpec) is the entry point (Design.over(fabric).optimizeMetros(spec) is the facade equivalent; the fluent MetroOptimizer.builder(fabric) only assembles a spec). A run gathers the facts once (context sub-package), measures the built-in objectives (design.objective: latency, cost, provider coverage, resilience, compliance), applies the built-in constraints (design.constraint), searches every admissible set of metros (design.solve.ExhaustiveSolver), analyses the answer's sensitivity (design.solve.SensitivityAnalysis) and places the workloads (design.placement). Money comes from one cost model (design.cost.RateCardCostModel).

The OptimizationResult carries the recommended option, the Pareto frontier, every constraint verdict, the sensitivity report, the placement and the calibrated latency factor, plus the views the Deployment Wizard, the exporters and the MCP server read.

Beta. When a workload depends on two clouds for which MulticloudEnvironmentCatalog lists a native provider-to-provider environment, the result carries an informational NATIVE_MULTICLOUD_ALTERNATIVE finding.

See Also:

• MetroOptimizer
• OptimizationResult
• DeploymentWizard

Related Packages

Package	Description
com.eqixiac.equinix.design	Value-add design engines built on top of the Equinix API clients: placement optimization, deployment planning, pricing/TCO analysis, peering intelligence, latency physics, and infrastructure-as-code export.
com.eqixiac.equinix.design.optimizer.context	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).
com.eqixiac.equinix.design.optimizer.enums	Enumerations that parameterize the Metro Optimization Engine: OptimizationStrategy (scoring weight presets), WorkloadType (workload archetypes with built-in profiles), LatencySensitivity (default per-workload placement ceilings), SiteRole (site importance multipliers), RedundancyTier (metro-count floors and region-diversity selection), ComplianceZone (region-based data-sovereignty zones with deployment-level AND semantics), ScoreCategory (the five scoring dimensions), and RiskSeverity (risk-finding levels).
com.eqixiac.equinix.design.optimizer.model	Immutable value types for the Metro Optimization Engine - the request side (sites, provider requirements, workload specs, constraints, scoring weights) and the result side (ranked recommendations, scores, topology, latency matrix, risk assessment, cost estimates).
com.eqixiac.equinix.design.optimizer.wizard	The Deployment Wizard: turns a metro OptimizationResult into an executable DeploymentPlan - Cloud Routers, provider connections, inter-metro backbone links, and routing protocols, with bandwidth-aware profile selection and honestly-reconciled pricing.

Classes

Class	Description
MetroOptimizer	The Metro Optimizer: which set of Equinix metros best serves a DesignSpec.
MetroOptimizer.Builder	Fluent convenience over DesignSpec: each call adds to the spec, MetroOptimizer.Builder.toSpec() returns it and MetroOptimizer.Builder.optimize() runs MetroOptimizer.forSpec(FabricGateway, DesignSpec).
MetroOptimizer.ConstraintsBuilder	Sets DesignConstraints and the budget.
MetroOptimizer.ProviderBuilder	Adds one CloudIntent.
MetroOptimizer.SiteBuilder	Adds one SiteIntent.
MetroOptimizer.WorkloadBuilder	Adds one WorkloadIntent.