Book Image

Network Programming with Rust

By : Abhishek Chanda
Book Image

Network Programming with Rust

By: Abhishek Chanda

Overview of this book

Rust is low-level enough to provide fine-grained control over memory while providing safety through compile-time validation. This makes it uniquely suitable for writing low-level networking applications. This book is divided into three main parts that will take you on an exciting journey of building a fully functional web server. The book starts with a solid introduction to Rust and essential networking concepts. This will lay a foundation for, and set the tone of, the entire book. In the second part, we will take an in-depth look at using Rust for networking software. From client-server networking using sockets to IPv4/v6, DNS, TCP, UDP, you will also learn about serializing and deserializing data using serde. The book shows how to communicate with REST servers over HTTP. The final part of the book discusses asynchronous network programming using the Tokio stack. Given the importance of security for modern systems, you will see how Rust supports common primitives such as TLS and public-key cryptography. After reading this book, you will be more than confident enough to use Rust to build effective networking software
Table of Contents (11 chapters)

Heading to tokio

The tokio ecosystem is an implementation of a network stack in Rust. It has all the major functionality of the standard library, the major difference being that it is non-blocking (most common calls do not block the current thread). This is achieved by using mio to do all the low-level heavy lifting, and using futures to abstract away long-running operations. The ecosystem has two basic crates, everything else being built around those:

  • tokio-proto provides primitives for building asynchronous servers and clients. This depends heavily on mio for low-level networking and on futures for abstraction.
  • tokio-core provides an event loop to run futures in and a number of related APIs. This is useful when an application needs fine-grained control over IO.

As we mentioned in the last section, one way to run futures is on an event loop. An event loop (called a reactor...