Go to file
Jon Gjengset 9691d0d379
Update tower-reconnect to std::future (#333)
This bumps tower-reconnect to 0.3.0-alpha.1

It also makes the tower-make version consistent
2019-09-10 11:48:01 -04:00
ci spawn-ready: Drives a service's readiness on an executor (#283) 2019-05-29 09:57:46 -07:00
tower Prep buffer and tower release (#305) 2019-07-19 14:21:07 -04:00
tower-balance Notify Pool when Services are dropped (#301) 2019-07-15 13:50:01 -04:00
tower-buffer Use the same version of pin-project everywhere (#329) 2019-09-09 16:31:40 -04:00
tower-discover Use the same version of pin-project everywhere (#329) 2019-09-09 16:31:40 -04:00
tower-filter Update tower-filter to std::future (#331) 2019-09-10 11:39:51 -04:00
tower-hedge Fix tower-hedge tests and add to CI (#287) 2019-05-28 13:33:42 -07:00
tower-layer Update tower-layer to std::future (#322) 2019-09-07 00:22:18 -04:00
tower-limit Use the same version of pin-project everywhere (#329) 2019-09-09 16:31:40 -04:00
tower-load Use the same version of pin-project everywhere (#329) 2019-09-09 16:31:40 -04:00
tower-load-shed Update tower-load-shed to std::future (#325) 2019-09-09 12:09:19 -04:00
tower-make Update tower-reconnect to std::future (#333) 2019-09-10 11:48:01 -04:00
tower-reconnect Update tower-reconnect to std::future (#333) 2019-09-10 11:48:01 -04:00
tower-retry Obviate need for as_mut to assert_request_eq (#327) 2019-09-09 15:28:41 -04:00
tower-service service: Add changelog entry for 0.3.0-alpha.1 2019-08-20 14:34:30 -04:00
tower-spawn-ready spawn-ready: Change layer to operate over MakeSpawnReady (#290) 2019-05-30 12:07:08 -07:00
tower-test Obviate need for as_mut to assert_request_eq (#327) 2019-09-09 15:28:41 -04:00
tower-timeout Update tower-timeout to std::future (#328) 2019-09-09 16:20:09 -04:00
tower-util Update `service_fn` to `std::future::Future` (#318) 2019-09-03 10:12:33 -04:00
.gitignore Initial commit 2016-08-26 16:26:03 -07:00
Cargo.toml Update tower-reconnect to std::future (#333) 2019-09-10 11:48:01 -04: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 Update `tower-service` to `std::future::Future` (#311) 2019-08-20 14:31:09 -04: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.