Package com.eqixiac.equinix.design.optimizer.context

package 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). Latencies carry their basis as a LatencyFigure.

Related Packages

Package	Description
com.eqixiac.equinix.design.optimizer	The Metro Optimizer: which set of Equinix metros best serves a DesignSpec, as a multi-objective search.
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.

Class	Description
CatalogDesignContext	The DesignContext of one Metro Optimizer run: the metro catalogue, Fabric's measured metro-to-metro round trips, cloud reachability per metro and the cost model, held in memory and never changed after CatalogDesignContext.Builder.build().
CatalogDesignContext.Builder	Assembles a CatalogDesignContext.
FabricCatalogLoader	Builds a CatalogDesignContext from live Fabric data, read-only, once per run: every page of GET /fabric/v4/metros (coordinates, region, country, geo scopes and zones, measured connectedMetros.avgLatency) and, when the spec names clouds, every page of the service profile search (which metros each cloud is reachable from).
LatencyFigure	One round-trip latency with where it came from.
LatencyFigure.Basis	How a latency figure was obtained.
ProviderCatalog	Resolves each CloudIntent of a spec to the Fabric service profiles that serve it and the metros those profiles publish: the source of reachableClouds per metro.