Swarm Reviews

7 Ratings
<a href='https://www.trustradius.com/static/about-trustradius-scoring' target='_blank' rel='nofollow noopener noreferrer'>trScore algorithm: Learn more.</a>
Score 7.6 out of 100

Do you work for this company? Learn how we help vendors

Overall Rating

Reviewer's Company Size

Last Updated

By Topic




Job Type


Filtered By:

Reviews (1-3 of 3)

Companies can't remove reviews or game the system. Here's why.
Anonymous | TrustRadius Reviewer
December 20, 2019

Swarm: Simplify Multiple Deployments

Score 7 out of 10
Vetted Review
Verified User
Review Source

Pros and Cons

  • Managing a cluster of micro-services.
  • Redundancy, fault-tolerance, and load balancing.
  • Small community - not a lot of information available outside of the documentation.
  • Logging - centralized logging for all applications is something we wish was available.
Read this authenticated review
Vlad VARNA | TrustRadius Reviewer
March 23, 2018

Hive Mind Your Frontend

Score 10 out of 10
Vetted Review
Verified User
Review Source

Pros and Cons

  • Creating complex containers using docker files which automate a lot of DevOps manual labor
  • Having some preconfigured containers to do fast tests
  • The swarm takes away a lot of the work you would need to do for high availability
  • Kitematic UI is still very limited in functionality
  • Containers on Windows are somewhat hit and miss, Linux is strongly recommended
  • Swarm interface is mostly command line
  • Some network limitations (like remote client IP passthrough)
Read Vlad VARNA's full review
Claudio Fernando Maciel | TrustRadius Reviewer
March 06, 2018

Docker Swarm - feature rich, simple to maintain

Score 10 out of 10
Vetted Review
Verified User
Review Source

Pros and Cons

  • Up and Down scaling of decentralized microservice instances
  • Remote maintenance and deployment of the existing docker based services
  • Smallest possible down time of our services upon the necessity of deployment, and maintenance routines
  • Simpler diagnostics: Today, with both Docker and Swarm, although it offers all the necessary diagnostics tools, as well as infos. The task of taking down one failing service, which in turn has failed due to some problem with some specific container, image, or network, seems a little bit of overhead. One needs to go all the way down the chain, find find by name or ID, until we get to the root of the problem. I think we could use a more 'intuitive' way of reaching the real cause of the problem, without the need to have to go through such a big stack of different commands.
  • Monitoring and logging tools: this one can arguably go together with the previously mentioned diagnostics 'issue'. Today, one can only find third party diagnostic, and monitoring tools. Sometimes, with the lack of a good indication, one has to go with lower-than-optimal tools whereby the job of logging and monitoring can be achieved.
  • Better, or more pervasive community, with some more in-depth whitepapers, documentation, or tutorials. Sometimes it's a little hard to come up with the solution for a particular requirement, for the lack of more in-depth documentation out there. Also, it's still discussed in some communities that Swarm is not yet 100% ready for business critical solutions. I think this kind of opinion/fear could be better dismissed, if more substantial documentation support could have been provided.
Read Claudio Fernando Maciel's full review

About Swarm

Docker Swarm is native clustering for Docker. It turns a pool of Docker hosts into a single, virtual Docker host. 
Categories:  Container Management

Swarm Technical Details

Operating Systems: Unspecified
Mobile Application:No