Go to file
João Oliveira cc58745952 update doc examples (#259) 2019-04-22 10:55:14 -07:00
ci Rename tower-util -> tower (#197) 2019-03-15 10:53:19 -07:00
tower Pin tower-hyper dep to a specific revision (#258) 2019-04-19 15:48:31 -07:00
tower-balance Promote service_fn to tower crate (#248) 2019-04-10 13:17:16 -07:00
tower-buffer buffer: Move buffer to service.rs and layer to layer.rs (#246) 2019-04-10 12:35:05 -07:00
tower-discover Add license field to all crates (#241) 2019-04-09 10:59:30 -07:00
tower-filter Add license field to all crates (#241) 2019-04-09 10:59:30 -07:00
tower-layer Move Tower to 2018 Edition (#238) 2019-04-08 20:11:09 -07:00
tower-limit Add license field to all crates (#241) 2019-04-09 10:59:30 -07:00
tower-load-shed Add license field to all crates (#241) 2019-04-09 10:59:30 -07:00
tower-reconnect Add license field to all crates (#241) 2019-04-09 10:59:30 -07:00
tower-retry Add license field to all crates (#241) 2019-04-09 10:59:30 -07:00
tower-service update doc examples (#259) 2019-04-22 10:55:14 -07:00
tower-test Add license field to all crates (#241) 2019-04-09 10:59:30 -07:00
tower-timeout Add license field to all crates (#241) 2019-04-09 10:59:30 -07:00
tower-util MakeConnection: rename Request generic to Target (#250) 2019-04-10 15:11:11 -07:00
.gitignore Initial commit 2016-08-26 16:26:03 -07:00
Cargo.toml Create `tower-test` and include tower-mock. (#237) 2019-04-07 20:42:18 -07:00
LICENSE Update the license for 2019 and tower contributors (#148) 2019-01-15 17:29:08 -05:00
README.md Create `tower-test` and include tower-mock. (#237) 2019-04-07 20:42:18 -07:00
azure-pipelines.yml Create `tower-test` and include tower-mock. (#237) 2019-04-07 20:42:18 -07:00

README.md

Tower

Tower is a library of modular and reusable components for building robust networking clients and servers.

Build Status Gitter

Overview

Tower aims to make it as easy as possible to build robust networking clients and servers. It is protocol agnostic, but is designed around a request / response pattern. If your protocol is entirely stream based, Tower may not be a good fit.

Project Layout

Tower consists of a number of components, each of which live in their own sub crates.

  • tower: The main user facing crate that provides batteries included tower services (docs).

  • tower-service: The foundational traits upon which Tower is built (docs).

  • tower-layer: The foundational trait to compose services together (docs).

  • tower-balance: A load balancer. Load is balanced across a number of services (docs).

  • tower-buffer: A buffering middleware. If the inner service is not ready to handle the next request, tower-buffer stores the request in an internal queue (docs).

  • tower-discover: Service discovery abstraction (docs).

  • tower-filter: Middleware that conditionally dispatch requests to the inner service based on a predicate (docs).

  • tower-limit: Middleware limiting the number of requests that are processed (docs).

  • tower-reconnect: Middleware that automatically reconnects the inner service when it becomes degraded (docs).

  • tower-retry: Middleware that retries requests based on a given Policy (docs).

  • tower-test: Testing utilies (docs).

  • tower-timeout: Middleware that applies a timeout to requests (docs).

  • tower-util: Miscellaneous additional utilities for Tower (docs).

Status

Currently, only tower-service, the foundational trait, has been released to crates.io. The rest of the library will be following shortly.

License

This project is licensed under the MIT license.

Contribution

Unless you explicitly state otherwise, any contribution intentionally submitted for inclusion in Tower by you, shall be licensed as MIT, without any additional terms or conditions.