libswarm is a toolkit for composing network services.
It defines a standard interface for services in a distributed system to communicate with each other. This lets you:
- Compose complex architectures from reusable building blocks
- Avoid vendor lock-in by swapping any service out with another
An extensive library of services is included, and you can also write your own using a simple API.
Here are some examples of what you can do with libswarm:
Aggregate all your Docker containers across multiple hosts and infrastructure providers, as if they were running on a single host.
Bridge your in-house DNS-based service discovery with that new shiny Consul deployment, without getting locked into either.
Swap in a new clustering and service discovery system, without changing any application code.
Collect logs across an in-house Mesos cluster, a Cloudfoundry deployment and individual servers staggered in 3 different datacenters, forward them to your legacy syslog deployment, then perform custom analytics on them.
Simulate your entire service topology in a single process, then scale it out simply by re-arranging adapters.
Organize your application as loosely coupled services from day 1, without over-engineering.
Maintainer: Ben Firshman
This service runs a Docker remote API server, allowing the Docker client and other Docker tools to control libswarm services.
Maintainer: Aanand Prasad
This service can be used to control a Docker Engine from libswarm services. It takes one argument, the Docker host to connect to. For example:
The debug service simply catches all messages and prints them on the terminal for inspection.
Testing libswarm with swarmd
Libswarm ships with a simple daemon which can control services in your distributed system.
Run swarmd without arguments to list available services:
Pass a service name as argument to load it:
You can pass arguments to the service, like a shell command:
./swarmd 'dockerserver tcp://localhost:4243'
You can call multiple services. They will be executed in parallel, with the output of each backend connected to the input of the next, just like unix pipelines.
This allows for very powerful composition.
./swarmd 'dockerserver tcp://localhost:4243' 'debug' 'dockerclient unix:///var/run/docker.sock'
Copyright and license
Code and documentation copyright 2013-2014 Docker, inc. Code released under the Apache 2.0 license. Docs released under Creative commons.