Book Image

Rust Web Programming

By : Maxwell Flitton
Book Image

Rust Web Programming

By: Maxwell Flitton

Overview of this book

Are safety and high performance a big concern for you while developing web applications? While most programming languages have a safety or speed trade-off, Rust provides memory safety without using a garbage collector. This means that with its low memory footprint, you can build high-performance and secure web apps with relative ease. This book will take you through each stage of the web development process, showing you how to combine Rust and modern web development principles to build supercharged web apps. You'll start with an introduction to Rust and understand how to avoid common pitfalls when migrating from traditional dynamic programming languages. The book will show you how to structure Rust code for a project that spans multiple pages and modules. Next, you'll explore the Actix Web framework and get a basic web server up and running. As you advance, you'll learn how to process JSON requests and display data from the web app via HTML, CSS, and JavaScript. You'll also be able to persist data and create RESTful services in Rust. Later, you'll build an automated deployment process for the app on an AWS EC2 instance and Docker Hub. Finally, you'll play around with some popular web frameworks in Rust and compare them. By the end of this Rust book, you'll be able to confidently create scalable and fast web applications with Rust.
Table of Contents (19 chapters)
1
Section 1:Setting Up the Web App Structure
4
Section 2:Processing Data and Managing Displays
8
Section 3:Data Persistence
12
Section 4:Testing and Deployment

Deploying our application image on dockerhub

Firstly, we have to manage our expectations. Similar to NGINX, automating deployment processes is a book in itself. In fact, there is a whole profession around it, called DevOps.

In this section, we will cover some basic automation processes. However, it has to be noted that this is not state of the art. Just like configuring the NGINX container in the previous section, we will cover enough information for you to get started with automated deployments. We are also just going to be using the docker-compose file on the server.

If you want to explore managing multiple containers, and multiple servers, then reading up on terraform or Kubernetes is advised. By the end of this section, we will have uploaded our application image to dockerhub, enabling it to be pulled multiple times from multiple areas. This makes switching to a different orchestration tool that is not docker-compose easier. In order to achieve this, we follow these steps...