website: use cases
This commit is contained in:
parent
a3c8374183
commit
a42661004d
|
@ -104,3 +104,16 @@ can be treated as a provider, allowing Terraform to request resources from them.
|
||||||
This allows Terraform to be used in layers: to setup the physical infrastructure
|
This allows Terraform to be used in layers: to setup the physical infrastructure
|
||||||
running the schedulers as well as onto the scheduled grid.
|
running the schedulers as well as onto the scheduled grid.
|
||||||
|
|
||||||
|
#### Multi-Cloud Deployment
|
||||||
|
|
||||||
|
It's often attractive to spread infrastructure across multiple clouds to increase
|
||||||
|
fault-tolerance. By using only a single region or cloud provider, fault tolerance
|
||||||
|
is limited by the availability of that provider. Having a multi-cloud deployment
|
||||||
|
allows for more graceful recovery of the loss of a region or entire provider.
|
||||||
|
|
||||||
|
Realizing multi-cloud deployments can be very challenging as many existing tools
|
||||||
|
for infrastructure management are cloud-specific. Terraform is cloud agnostic,
|
||||||
|
and allows a single configuration to be used to manage multiple providers, and
|
||||||
|
to even handle cross-cloud dependcies. This simplifies management and orchestration,
|
||||||
|
helping operators build large scale multi-cloud infrastructures.
|
||||||
|
|
||||||
|
|
Loading…
Reference in New Issue