Terraform vs Visual Studio: What are the differences?
Terraform: Describe your complete infrastructure as code and build resources across providers. With Terraform, you describe your complete infrastructure as code, even as it spans multiple service providers. Your servers may come from AWS, your DNS may come from CloudFlare, and your database may come from Heroku. Terraform will build all these resources across all these providers in parallel; Visual Studio: State-of-the-art tools and services that you can use to create great apps for devices, the cloud, and everything in between. Visual Studio is a suite of component-based software development tools and other technologies for building powerful, high-performance applications.
Terraform can be classified as a tool in the "Infrastructure Build Tools" category, while Visual Studio is grouped under "Integrated Development Environment".
"Infrastructure as code" is the top reason why over 81 developers like Terraform, while over 270 developers mention "Intellisense, ui" as the leading cause for choosing Visual Studio.
Terraform is an open source tool with 17.7K GitHub stars and 4.83K GitHub forks. Here's a link to Terraform's open source repository on GitHub.
According to the StackShare community, Visual Studio has a broader approval, being mentioned in 676 company stacks & 1010 developers stacks; compared to Terraform, which is listed in 509 company stacks and 312 developer stacks.
What is Terraform?
What is Visual Studio?
Need advice about which tool to choose?Ask the StackShare community!
Sign up to add, upvote and see more prosMake informed product decisions
What are the cons of using Terraform?
What are the cons of using Visual Studio?
Sign up to get full access to all the companiesMake informed product decisions
Sign up to get full access to all the tool integrationsMake informed product decisions
LaunchDarkly is almost a five year old company, and our methodology for deploying was state of the art... for 2014. We recently undertook a project to modernize the way we #deploy our software, moving from Ansible-based deploy scripts that executed on our local machines, to using Spinnaker (along with Terraform and Packer) as the basis of our deployment system. We've been using Armory's enterprise Spinnaker offering to make this project a reality.
We use Terraform because we needed a way to automate the process of building and deploying feature branches. We wanted to hide the complexity such that when a dev creates a PR, it triggers a build and deployment without the dev having to worry about any of the 'plumbing' going on behind the scenes. Terraform allows us to automate the process of provisioning DNS records, Amazon S3 buckets, Amazon EC2 instances and AWS Elastic Load Balancing (ELB)'s. It also makes it easy to tear it all down when finished. We also like that it supports multiple clouds, which is why we chose to use it over AWS CloudFormation.
I use Visual Studio because it provides me best default configuration for development. Less choice helps me concentrate on the product. In a sense it is iPhone of software development for me. When my laptop broke, I just download latest version of VS and start coding without any configuration. For sure it has best editor in terms of perceived responsiveness. Could not say the same for IntelliJ IDEA unfortunately.
I use Terraform because it hits the level of abstraction pocket of being high-level and flexible, and is agnostic to cloud platforms. Creating complex infrastructure components for a solution with a UI console is tedious to repeat. Using low-level APIs are usually specific to cloud platforms, and you still have to build your own tooling for deploying, state management, and destroying infrastructure.
However, Terraform is usually slower to implement new services compared to cloud-specific APIs. It's worth the trade-off though, especially if you're multi-cloud. I heard someone say, "We want to preference a cloud, not lock in to one." Terraform builds on that claim.
Terraform Google Cloud Deployment Manager AWS CloudFormation
Our base infrastructure is composed of Debian based servers running in Amazon EC2 , asset storage with Amazon S3 , and Amazon RDS for Aurora and Redis under Amazon ElastiCache for data storage.
We are starting to work in automated provisioning and management with Terraform , Packer , and Ansible .
Supports many languages, wide variety of plugins
We are an ASP.NET shop, so it is fitting that we use Visual Studio. The biggest advantage that VS gives us is the first-class debugger, and the ReSharper refactoring tools. We do use Sublime, Brackets, Vim, Emacs, and other editors in conjunction with VS since VS does can take a long time to load.
An IDE which I use for at least ten years now. Roslyn is getting better and better, but VS Code seems better now. A bit obsolete concept, but the extra tools (like git integration, azure browsing, preset projects and solutions) makes it still very useful.
PrometheanTV builds applications and services utilizing a variety of languages and technologies. The Visual Studio IDE is used by various technical staff to build software on a variety of languages supported by the IDE including C#, HTML/CSS/JS, etc.
been a while since i've used visual studio. developed the tools for superman returns in it. liked the debugging but not much else. only played with the newest version a couple of times.
Terraform makes it so easy to deploy AWS and Google Cloud services, with the declarative approach avoiding so many headaches of manual work and possible mistakes.
Best open source, good replacement for Visual Studio. I'm using it as my development environment in C# and Dynamics 365 Business Central (extension development).
- Infrastructure as Code.
- Central tool to deploy all infratructure: AWS, CloudFlare, StatusCake
The entire AWS environments is described and setup using Terraform.