---
title: "Discussion on \"Introduction to the Tower library\" | Hashnode"
description: "Discussion on \"Introduction to the Tower library\". One of the components of my OpenTelemetry demo is a Rust application built with the Axum web framework. In its description, axum mentions:\n\naxum doesn't have its own middleware system but instead uses tower::Service. This means axum gets timeouts, tr..."
url: "https://hashnode.com/posts/introduction-to-the-tower-library/64e71c91a22cd603433ce613"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [Introduction to the Tower library](https://frankel.hashnode.dev/introduction-to-the-tower-library?utm_source=hashnode&utm_medium=feed)

One of the components of my OpenTelemetry demo is a Rust application built with the Axum web framework. In its description, axum mentions: axum doesn't have its own middleware system but instead uses tower::Service. This means axum gets timeouts, tr...

Aug 24, 2023 · 4 min read · frankel.hashnode.dev  
Read the article

-   [#rust](https://hashnode.com/tag/rust)
-   [#tower](https://hashnode.com/tag/tower)
-   [#functional-programming](https://hashnode.com/tag/functional-programming)

## Written by

[Nicolas Fränkel](https://hashnode.com/@nfrankel)

@nfrankel · Geneva

  
[View profile](https://hashnode.com/@nfrankel)

Developer Advocate

Technologist focusing on cloud-native technologies, DevOps, CI/CD pipelines, and system observability. His focus revolves around creating technical content, delivering talks, and engaging with developer communities to promote the adoption of modern software practices. With a strong background in software, he has worked extensively with the JVM, applying his expertise across various industries. In addition to his technical work, he is the author of several books and regularly shares insights through his blog and open-source contributions.

## Responses

Markdown supported · ⌘↵ to post

No responses yet.
