You're reading from Speed Up Your Python with Rust Optimize Python performance by creating Python pip modules in Rust with PyO3

Product type Paperback

Published in Jan 2022

Publisher Packt

ISBN-13 9781801811446

Length 384 pages

Edition 1st Edition

Languages

Python

Tools

Docker

Concepts

Software Architecture

Author (1):

Maxwell Flitton

View More author details

Table of Contents (16) Chapters

Preface

1. Section 1: Getting to Understand Rust

2. Chapter 1: An Introduction to Rust from a Python Perspective FREE CHAPTER

3. Chapter 2: Structuring Code in Rust

4. Chapter 3: Understanding Concurrency

5. Section 2: Fusing Rust with Python

6. Chapter 4: Building pip Modules in Python

7. Chapter 5: Creating a Rust Interface for Our pip Module

8. Chapter 6: Working with Python Objects in Rust

9. Chapter 7: Using Python Modules with Rust

10. Chapter 8: Structuring an End-to-End Python Package in Rust

11. Section 3: Infusing Rust into a Web Application

12. Chapter 9: Structuring a Python Flask App for Rust

13. Chapter 10: Injecting Rust into a Python Flask App

14. Chapter 11: Best Practices for Integrating Rust

15. Other Books You May Enjoy

Chapter 9: Structuring a Python Flask App for Rust

In the previous chapter, we managed to solve a real-world problem with Rust. However, we also learned an important lesson, that is, the good implementation of code, such as adding vectors or merging dataframes, along with third-party modules, such as NumPy, can outperform badly implemented self-coded Rust solutions. However, we know that comparing implementation to implementation, Rust is a lot faster than Python. We already understand how to fuse Rust with a standard Python script. However, Python is used for more than just running scripts. A popular use for Python is in web applications.

In this chapter, we will build a Flask web application with NGINX, a database, and a message bus implemented by the Celery package. This message bus will allow our application to process heavy tasks in the background while we return a web HTTP request. The web application and message bus will be wrapped in Docker containers and deployed to docker...