Package com.eqixiac.equinix.design.value.tco


package com.eqixiac.equinix.design.value.tco
Design-time total-cost-of-ownership comparison across three DeploymentArchetypes — public cloud over the internet, on-premises, and Equinix-interconnected. The entry point is fabric.tcoComparison() (or TcoCalculator.builder(fabric)), a fluent TcoCalculator.Builder terminated by compare(), which yields a TcoComparison of per-archetype CostBreakdowns. Archetypes are ranked by total cost over the commitment term (MRC × months + setup), so one-time charges are never ignored in the recommendation.

Prices come from the layered rate-card architecture in com.eqixiac.equinix.design.value.ratecard: by default live Equinix Fabric pricing backed by bundled reference figures, replaceable with a caller-supplied card. Each breakdown records which components priced (isPriced()), carries the currency its own components reconciled to, and — per the layer's currency-honesty rule — figures in differing currencies are never summed and no FX rate is fabricated: a mixed-currency archetype is reported unpriced with per-currency subtotals, and the baseline-versus-recommended saving is left null when the two sides' currencies differ.

See Also:
  • Class
    Description
    The modelled monthly and one-time cost of a single DeploymentArchetype, broken out into named line items.
    The three deployment approaches the TCO model compares.
    Fluent calculator that compares the total cost of ownership of a workload across the three DeploymentArchetypes — public cloud over the internet, on-prem, and Equinix-interconnected — and reports which is cheapest over the commitment term (monthly recurring × term months + one-time setup) and by how much.
    Fluent configuration for a TCO comparison, terminated by TcoCalculator.Builder.compare().
    The result of a TcoCalculator run: a side-by-side cost comparison of the requested DeploymentArchetypes, the recommended approach — the lowest total cost over the commitment term (MRC × months + NRC), so one-time setup charges count — and the saving of the recommended approach versus the public-cloud-over-internet baseline, both per month and over the term.