Vagrant vs XenServer: What are the differences?
Developers describe Vagrant as "A tool for building and distributing development environments". Vagrant provides the framework and configuration format to create and manage complete portable development environments. These development environments can live on your computer or in the cloud, and are portable between Windows, Mac OS X, and Linux. On the other hand, XenServer is detailed as "An open source virtualization platform". It is a leading virtualization management platform optimized for application, desktop and server virtualization infrastructures. It is used in the world's largest clouds and enterprises.
Vagrant and XenServer belong to "Virtual Machine Management" category of the tech stack.
Vagrant is an open source tool with 18.7K GitHub stars and 3.77K GitHub forks. Here's a link to Vagrant's open source repository on GitHub.
Airbnb, Shopify, and Coursera are some of the popular companies that use Vagrant, whereas XenServer is used by Infoxchange, GameDuell, and Leonis Holding. Vagrant has a broader approval, being mentioned in 1051 company stacks & 3207 developers stacks; compared to XenServer, which is listed in 9 company stacks and 7 developer stacks.
What is Vagrant?
What is XenServer?
Need advice about which tool to choose?Ask the StackShare community!
Why do developers choose XenServer?
Sign up to add, upvote and see more prosMake informed product decisions
What are the cons of using XenServer?
Sign up to get full access to all the companiesMake informed product decisions
What tools integrate with XenServer?
Sign up to get full access to all the tool integrationsMake informed product decisions
"The best way to ensure that local testing was possible was to normalize people’s dev environments. For this we chose Vagrant. This, combined with Chef, allows us to do our local dev in sandboxed Linux instances running locally via VirtualBox in a configuration as similar to production as possible. In addition to making dev environment setup much easier than it used to be, this ensures that each engineer has a consistent environment that is ready to run tests out of the box. The user SSHs into the local linux server and runs spec commands like they would on their host OS, and generally everything Just Works. Most people on our team combine this with Zeus, which allows the Rails environment to be preloaded for lightning fast (relatively speaking) test runs. Both Vagrant and Zeus have their share of issues, but in practice we’ve found them to be a huge time saver."
Not blazing fast but we pick Vagrant for all our projects because the console mode without gui leads to a low consumption of ram memory making it the best way for DevOps ready environment requiring less configuration.
Vagrant allows me to ensure that anyone I'm collaborating with will be able to test my web application in the same environment. I also use Vagrant to setup VMs that I can use to refine my Capistrano recipes.
We use Virtualbox in combination with Vagrant during development to ensure a consistent test/development environment. This helps to reduce the number of defects when our software goes to production.