BrowserStack vs Docker Swarm: What are the differences?
BrowserStack: Instant access to a lab of 1000+ real mobile and desktop browsers for testing. Live, Web-Based Browser Testing Instant access to all real mobile and desktop browsers. Say goodbye to your lab of devices and virtual machines; Docker Swarm: Native clustering for Docker. Turn a pool of Docker hosts into a single, virtual host. Swarm serves the standard Docker API, so any tool which already communicates with a Docker daemon can use Swarm to transparently scale to multiple hosts: Dokku, Compose, Krane, Deis, DockerUI, Shipyard, Drone, Jenkins... and, of course, the Docker client itself.
BrowserStack can be classified as a tool in the "Browser Testing" category, while Docker Swarm is grouped under "Container Tools".
"Multiple browsers" is the top reason why over 121 developers like BrowserStack, while over 44 developers mention "Docker friendly" as the leading cause for choosing Docker Swarm.
Docker Swarm is an open source tool with 5.63K GitHub stars and 1.11K GitHub forks. Here's a link to Docker Swarm's open source repository on GitHub.
According to the StackShare community, BrowserStack has a broader approval, being mentioned in 579 company stacks & 238 developers stacks; compared to Docker Swarm, which is listed in 83 company stacks and 38 developer stacks.
What is BrowserStack?
What is Docker Swarm?
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 BrowserStack?
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
Visual Studio Code worked really well for us as well, it worked well with all our polyglot services and the .Net core integration had great cross-platform developer experience (to be fair, F# was a bit trickier) - actually, each of our team members used a different OS (Ubuntu, macos, windows). Our production deployment ran for a time on Docker Swarm until we've decided to adopt Kubernetes with almost seamless migration process.
After our positive experience of running .Net core workloads in containers and developing Tweek's .Net services on non-windows machines, C# had gained back some of its popularity (originally lost to Node.js), and other teams have been using it for developing microservices, k8s sidecars (like https://github.com/Soluto/airbag), cli tools, serverless functions and other projects...
I am working on #OpenSource file uploader. The uploader is the widget that other developers embed in their apps. It should work well in different browsers and on different devices. BrowserStack and Sauce Labs help to achieve that. I can test the uploader in many varieties of browsers+OS only used my browser without virtual machines.
It's incredible how much this service has increased my productivity when it comes to testing new features in multiple browsers. And not only multiple browsers, multiple operating systems as well! And really LOVE that you can run it locally.
We only really need this for IE support
We use BrowserStack to run end to end tests with Selenium on our dashboard. It runs automatically before every deployment and cancels it if anything is out of place.
BrowserStack is used by our development and support teams during QA and to try and reproduce bugs.
Manually and automatically test our web and mobile apps.