Uses of Class
com.eqixiac.equinix.core.model.MetroId

Packages that use MetroId
Package
Description
Core model interfaces and base types for the Equinix Java SDK.
The Metro Optimizer: which set of Equinix metros best serves a DesignSpec, as a multi-objective search.
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).
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).
Peering Intelligence: interconnection analysis combining PeeringDB IX/facility data with the live Equinix Fabric catalog.
Result value types for Peering Intelligence, all Lombok @Value (get-prefixed accessors) unless a hand-written accessor is documented.
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.
Extension points of the design engines.
Fabric domain client interfaces for the Equinix Java SDK.
 
Fabric domain model interfaces for the Equinix Java SDK.