github.com/ns1/terraform@v0.7.10-0.20161109153551-8949419bef40/website/source/intro/vs/boto.html.markdown (about)

     1  ---
     2  layout: "intro"
     3  page_title: "Terraform vs. Boto, Fog, etc."
     4  sidebar_current: "vs-other-boto"
     5  description: |-
     6    Libraries like Boto, Fog, etc. are used to provide native access to cloud providers and services by using their APIs. Some libraries are focused on specific clouds, while others attempt to bridge them all and mask the semantic differences. Using a client library only provides low-level access to APIs, requiring application developers to create their own tooling to build and manage their infrastructure.
     7  ---
     8  
     9  # Terraform vs. Boto, Fog, etc.
    10  
    11  Libraries like Boto, Fog, etc. are used to provide native access
    12  to cloud providers and services by using their APIs. Some
    13  libraries are focused on specific clouds, while others attempt
    14  to bridge them all and mask the semantic differences. Using a client
    15  library only provides low-level access to APIs, requiring application
    16  developers to create their own tooling to build and manage their infrastructure.
    17  
    18  Terraform is not intended to give low-level programmatic access to
    19  providers, but instead provides a high level syntax for describing
    20  how cloud resources and services should be created, provisioned, and
    21  combined. Terraform is very flexible, using a plugin-based model to
    22  support providers and provisioners, giving it the ability to support
    23  almost any service that exposes APIs.
    24