Uses of Package
com.eqixiac.equinix.design.spec

Package
Description
Root package for the Equinix Java SDK.
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 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).
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.
Peering Intelligence: interconnection analysis combining PeeringDB IX/facility data with the live Equinix Fabric catalog.
The Design Decision Record: the one document an architect hands to a review board for a DesignSpec.
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.
The shared design document every design engine reads: DesignSpec.
Extension points of 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.