Weaveworks
| Private | |
| ISIN | 🆔 |
| Industry | Containers |
| Founded 📆 | 2014 |
| Founders 👔 | Alexis Richardson Matthias Radestock |
| Headquarters 🏙️ | London, England |
Area served 🗺️ | |
| Members | |
Number of employees | |
| 🌐 Website | www.weave.works |
| 📇 Address | |
| 📞 telephone | |
Intro
Weaveworks’ project Weave Net and collaborative efforts in the open-source networking space led to both the creation of the dominant open container network API spec: CNI (which they co-founded with CoreOS and others), now used in Kubernetes & Mesos, and separately the Docker container plugin scheme: libvolume and libnetwork (co-presented at DockerCon in 2015 with Docker and ClusterHQ).
Technology
Weaveworks contributes to several open-source project ecosystems, including: Docker and Kubernetes, and originated the open-source projects: Weave Net, Weave Scope, Weave Cortex, Weave Flux.
Weave Net
One of the first container-specific overlay networks. Its decentralised, mesh network architecture sets it apart from other projects in the same space. It implements a gossip protocol that provides membership, unicast, and broadcast functionality with eventually-consistent semantics. In CAP terms, it is AP: highly available and partition-tolerant. It works in situations where there is only partial connectivity, i.e., data is transparently routed across multiple hops when there is no direct connection between peers. It copes with partitions and partial network failure. It can be easily bootstrapped, typically only requiring knowledge of a single existing peer in the mesh to join. It has built-in shared-secret authentication and encryption.
Weave Scope
An open-source tool for visualising topologies of applications running in various container orchestration platforms, such as Docker, Kubernetes, and Mesos. Weave Scope automatically generates a map of your application, enabling you to understand, monitor, and control your containerized, microservices-based application.
Weave Flux
An open-source tool for automating deployment of applications packaged in Docker containers into orchestration platforms such as Kubernetes. Flux is a stateless operator that runs inside the cluster and pulls from an external Git repository. It implements the GitOps approach to managing application releases and automatically ensures that the state of a cluster matches what is specified in version control.
Weave Cortex
An open-source project that provides a service backend enabling Prometheus data to be persisted to various cloud data storage services. It provides horizontally scalable, long-term storage for Prometheus metrics when used as a remote write destination, and a horizontally scalable, Prometheus-compatible query API. Cortex is being used by Weaveworks, Freshtracks, Kausal, and several other organisations.
Weave Cloud
Weave Cloud is a commercial offering aimed at simplifying containers and microservices, specifically providing value-add for DevOps in Kubernetes via an integrated platform where GitHub meets operations to accelerate the delivery of applications on the cloud.
History / Company
Weaveworks, the company, was founded in 2014 by Alexis Richardson (CEO) and Matthias Radestock (CTO) and is backed by Google Ventures and Accel Partners with $25 million in Series A and B funding. It was one of the first members to join the Cloud Native Computing Forum (CNCF), where Richardson also serves as Chair of the Technical Committee.
Alexis is the co-founder and CEO of Weaveworks and the co-founder of the Coed:Code meetups. Previously, he was at Pivotal, as head of products for Spring, RabbitMQ, Redis, Apache Tomcat, and vFabric. Alexis was responsible for resetting the product direction of Spring and transitioning the vFabric business from VMware. Alexis co-founded RabbitMQ and was CEO of the Rabbit company, acquired by VMware in 2010, where he worked on numerous cloud platforms.
Matthias Radestock is the co-founder and CTO of Weaveworks. He previously co-founded RabbitMQ and a number of other software technology start-ups. Matthias has a PhD in Computer Science from Imperial College and has spent much of the past 20 years working with distributed systems.
This article "Weaveworks" is from Wikipedia. The list of its authors can be seen in its historical and/or the page Edithistory:Weaveworks. Articles copied from Draft Namespace on Wikipedia could be seen on the Draft Namespace of Wikipedia and not main one.
