Uses of Package
com.eqixiac.equinix

Packages that use com.eqixiac.equinix
Package
Description
Root package for the Equinix Java SDK.
Core client infrastructure for the Equinix Java SDK.
 
Estate analysis: looks at what a customer already runs on Equinix and produces a priced, evidence-backed improvement report.
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).
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.
Value types for the Deployment Wizard - the plan itself and everything it is made of, plus the execution-side inputs and outcomes.
Peering Intelligence: interconnection analysis combining PeeringDB IX/facility data with the live Equinix Fabric catalog.
The deployment-plan lifecycle: plan as data, drift detection, idempotent and resumable reconcile, and safe rollback.
The Design Decision Record: the one document an architect hands to a review board for a DesignSpec.
Failure analysis of a design.
Rate cards: pluggable sources of unit prices for the design-time cost, savings, and TCO models.
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.
The embedded Equinix Intelligence MCP Server - a community Model Context Protocol server, not affiliated with or endorsed by Equinix, and separate from Equinix's official Fabric MCP server.
  • Class
    Description
    The primary entry point for accessing Equinix Customer Portal APIs.
    A root-level entry point that gathers the SDK's value-add design capabilities - Metro Optimizer, Deployment Wizard, Peering Intelligence, Savings Calculator, and TCO comparison - in one discoverable place, alongside the API-domain clients (Fabric, NetworkEdge, ...).
    A single Equinix session that owns one authenticated core client - a single OAuth token and a single HTTP connection pool - and vends every domain client over it.
    The base class for all Equinix SDK domain entry points.
    Construction-time options for an Equinix client or Equinix session, passed instead of the bare (credentials, sandbox) arguments when finer control is needed:
    The primary entry point for accessing the Equinix Fabric APIs.
    Narrow capability view of Fabric that the value-add design engines depend on - the metro/service-profile/cloud-router/connection/routing-protocol resources the optimizer, deployment wizard, and peering intelligence actually use.
    The primary entry point for accessing the Equinix Identity and Access Management (IAM) API (Access v1) - Equinix's attribute-based access control (ABAC) and role-based access control (RBAC) plane.
    The primary entry point for accessing Equinix IBX SmartView APIs.
    The primary entry point for accessing the Equinix Internet Access (EIA) v2 API.
    The primary entry point for accessing the Equinix Network Edge APIs.
    The primary entry point for accessing Equinix Projects APIs.
    The primary entry point for accessing the Equinix Security Token Service (STS) API (STS v1).
  • Class
    Description
    The base class for all Equinix SDK domain entry points.
  • Class
    Description
    The base class for all Equinix SDK domain entry points.
  • Class
    Description
    The primary entry point for accessing the Equinix Fabric APIs.
    The primary entry point for accessing the Equinix Network Edge APIs.
  • Class
    Description
    Narrow capability view of Fabric that the value-add design engines depend on - the metro/service-profile/cloud-router/connection/routing-protocol resources the optimizer, deployment wizard, and peering intelligence actually use.
  • Class
    Description
    Narrow capability view of Fabric that the value-add design engines depend on - the metro/service-profile/cloud-router/connection/routing-protocol resources the optimizer, deployment wizard, and peering intelligence actually use.
  • Class
    Description
    Narrow capability view of Fabric that the value-add design engines depend on - the metro/service-profile/cloud-router/connection/routing-protocol resources the optimizer, deployment wizard, and peering intelligence actually use.
  • Class
    Description
    Narrow capability view of Fabric that the value-add design engines depend on - the metro/service-profile/cloud-router/connection/routing-protocol resources the optimizer, deployment wizard, and peering intelligence actually use.
  • Class
    Description
    Narrow capability view of Fabric that the value-add design engines depend on - the metro/service-profile/cloud-router/connection/routing-protocol resources the optimizer, deployment wizard, and peering intelligence actually use.
  • Class
    Description
    Narrow capability view of Fabric that the value-add design engines depend on - the metro/service-profile/cloud-router/connection/routing-protocol resources the optimizer, deployment wizard, and peering intelligence actually use.
  • Class
    Description
    Narrow capability view of Fabric that the value-add design engines depend on - the metro/service-profile/cloud-router/connection/routing-protocol resources the optimizer, deployment wizard, and peering intelligence actually use.
  • Class
    Description
    Narrow capability view of Fabric that the value-add design engines depend on - the metro/service-profile/cloud-router/connection/routing-protocol resources the optimizer, deployment wizard, and peering intelligence actually use.
  • Class
    Description
    Narrow capability view of Fabric that the value-add design engines depend on - the metro/service-profile/cloud-router/connection/routing-protocol resources the optimizer, deployment wizard, and peering intelligence actually use.
  • Class
    Description
    Narrow capability view of Fabric that the value-add design engines depend on - the metro/service-profile/cloud-router/connection/routing-protocol resources the optimizer, deployment wizard, and peering intelligence actually use.
  • Class
    Description
    Narrow capability view of Fabric that the value-add design engines depend on - the metro/service-profile/cloud-router/connection/routing-protocol resources the optimizer, deployment wizard, and peering intelligence actually use.
  • Class
    Description
    The primary entry point for accessing Equinix Customer Portal APIs.
    A root-level entry point that gathers the SDK's value-add design capabilities - Metro Optimizer, Deployment Wizard, Peering Intelligence, Savings Calculator, and TCO comparison - in one discoverable place, alongside the API-domain clients (Fabric, NetworkEdge, ...).
    A single Equinix session that owns one authenticated core client - a single OAuth token and a single HTTP connection pool - and vends every domain client over it.
    Narrow capability view of Fabric that the value-add design engines depend on - the metro/service-profile/cloud-router/connection/routing-protocol resources the optimizer, deployment wizard, and peering intelligence actually use.
    The primary entry point for accessing Equinix IBX SmartView APIs.
    The primary entry point for accessing the Equinix Network Edge APIs.