StackShareStackShare
Follow on
StackShare

Discover and share technology stacks from companies around the world.

Follow on

© 2025 StackShare. All rights reserved.

Product

  • Stacks
  • Tools
  • Feed

Company

  • About
  • Contact

Legal

  • Privacy Policy
  • Terms of Service
  1. Stackups
  2. Application & Data
  3. Container Registry
  4. Container Tools
  5. Weave vs XMPP

Weave vs XMPP

OverviewComparisonAlternatives

Overview

Weave
Weave
Stacks50
Followers72
Votes7
XMPP
XMPP
Stacks71
Followers138
Votes0

Weave vs XMPP: What are the differences?

Developers describe Weave as "Weave creates a virtual network that connects Docker containers deployed across multiple hosts". Weave can traverse firewalls and operate in partially connected networks. Traffic can be encrypted, allowing hosts to be connected across an untrusted network. With weave you can easily construct applications consisting of multiple containers, running anywhere. On the other hand, XMPP is detailed as "An open XML technology for real-time communication". It is a set of open technologies for instant messaging, presence, multi-party chat, voice and video calls, collaboration, lightweight middleware, content syndication, and generalized routing of XML data.

Weave and XMPP can be primarily classified as "Container" tools.

Weave is an open source tool with 5.59K GitHub stars and 524 GitHub forks. Here's a link to Weave's open source repository on GitHub.

Excursiopedia, Tutum, and Udacity are some of the popular companies that use Weave, whereas XMPP is used by Mendix, Vidyo.io, and Relayo. Weave has a broader approval, being mentioned in 14 company stacks & 21 developers stacks; compared to XMPP, which is listed in 7 company stacks and 5 developer stacks.

Share your Stack

Help developers discover the tools you use. Get visibility for your team's tech choices and contribute to the community's knowledge.

View Docs
CLI (Node.js)
or
Manual

Detailed Comparison

Weave
Weave
XMPP
XMPP

Weave can traverse firewalls and operate in partially connected networks. Traffic can be encrypted, allowing hosts to be connected across an untrusted network. With weave you can easily construct applications consisting of multiple containers, running anywhere.

It is a set of open technologies for instant messaging, presence, multi-party chat, voice and video calls, collaboration, lightweight middleware, content syndication, and generalized routing of XML data.

Virtual Ethernet Switch;Application isolation;Security;Host network integration;Service export;Service import;Multi-cloud networking;Multi-hop routing;Dynamic topologies;Container mobility;Fault tolerance
-
Statistics
Stacks
50
Stacks
71
Followers
72
Followers
138
Votes
7
Votes
0
Pros & Cons
Pros
  • 3
    Easy setup
  • 3
    Seamlessly with mesos/marathon
  • 1
    Seamless integration with application layer
No community feedback yet
Integrations
Docker
Docker
boot2docker
boot2docker
Java
Java
Python
Python
JavaScript
JavaScript

What are some alternatives to Weave, XMPP?

Kubernetes

Kubernetes

Kubernetes is an open source orchestration system for Docker containers. It handles scheduling onto nodes in a compute cluster and actively manages workloads to ensure that their state matches the users declared intentions.

Rancher

Rancher

Rancher is an open source container management platform that includes full distributions of Kubernetes, Apache Mesos and Docker Swarm, and makes it simple to operate container clusters on any cloud or infrastructure platform.

Kafka

Kafka

Kafka is a distributed, partitioned, replicated commit log service. It provides the functionality of a messaging system, but with a unique design.

RabbitMQ

RabbitMQ

RabbitMQ gives your applications a common platform to send and receive messages, and your messages a safe place to live until received.

Docker Compose

Docker Compose

With Compose, you define a multi-container application in a single file, then spin your application up in a single command which does everything that needs to be done to get it running.

Docker Swarm

Docker Swarm

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.

Celery

Celery

Celery is an asynchronous task queue/job queue based on distributed message passing. It is focused on real-time operation, but supports scheduling as well.

Tutum

Tutum

Tutum lets developers easily manage and run lightweight, portable, self-sufficient containers from any application. AWS-like control, Heroku-like ease. The same container that a developer builds and tests on a laptop can run at scale in Tutum.

Amazon SQS

Amazon SQS

Transmit any volume of data, at any level of throughput, without losing messages or requiring other services to be always available. With SQS, you can offload the administrative burden of operating and scaling a highly available messaging cluster, while paying a low price for only what you use.

NSQ

NSQ

NSQ is a realtime distributed messaging platform designed to operate at scale, handling billions of messages per day. It promotes distributed and decentralized topologies without single points of failure, enabling fault tolerance and high availability coupled with a reliable message delivery guarantee. See features & guarantees.

Related Comparisons

GitHub
Bitbucket

Bitbucket vs GitHub vs GitLab

Bootstrap
Materialize

Bootstrap vs Materialize

Laravel
Django

Django vs Laravel vs Node.js

Bootstrap
Foundation

Bootstrap vs Foundation vs Material UI

Node.js
Spring Boot

Node.js vs Spring-Boot