Book Image

Speed Up Your Python with Rust

By : Maxwell Flitton
5 (2)
Book Image

Speed Up Your Python with Rust

5 (2)
By: Maxwell Flitton

Overview of this book

Python has made software development easier, but it falls short in several areas including memory management that lead to poor performance and security. Rust, on the other hand, provides memory safety without using a garbage collector, which means that with its low memory footprint, you can build high-performant and secure apps relatively easily. However, rewriting everything in Rust can be expensive and risky as there might not be package support in Rust for the problem being solved. This is where Python bindings and pip come in. This book will help you, as a Python developer, to start using Rust in your Python projects without having to manage a separate Rust server or application. Seeing as you'll already understand concepts like functions and loops, this book covers the quirks of Rust such as memory management to code Rust in a productive and structured manner. You'll explore the PyO3 crate to fuse Rust code with Python, learn how to package your fused Rust code in a pip package, and then deploy a Python Flask application in Docker that uses a private Rust pip module. Finally, you'll get to grips with advanced Rust binding topics such as inspecting Python objects and modules in Rust. By the end of this Rust book, you'll be able to develop safe and high-performant applications with better concurrency support.
Table of Contents (16 chapters)
1
Section 1: Getting to Understand Rust
5
Section 2: Fusing Rust with Python
11
Section 3: Infusing Rust into a Web Application

Answers

  1. Directly connecting to a database with Rust reduces the amount of code we must write as we do not have to inspect the Python objects that are returned from the Python database call. We also do not have to package data into Python objects before inserting them into the database. This essentially removes a whole layer of code that we must write when interacting with the database.
  2. If someone gets hold of our image, they can access the layers of the build. As a result, they can access the arguments that have been passed into the build. This will mean that they can see the credentials we use to log in.
  3. We used the diesel crate to connect to the database and automatically print the schemas and models based on the database it connects to. We can do this repeatedly to keep up to date with new database migrations.  
  4. We must remember that our Rust database package is an appendage to our Python web application. Our Python web application has already loaded...