A CRUD Server
Explore how to create a robust CRUD server in Rust focusing on core operations such as creating, reading, updating, and deleting employee records. Understand project structure, route handling with warp, business logic separation, and thread-safe in-memory storage using Arc and Mutex for asynchronous environments.
In this lesson, we’ll learn how to create a simple CRUD server and structure a Rust project.
Once again, we’ll work on a simple employee management system as our test project.
A plan of action
A CRUD server needs at least four different routes to create, read, update, and delete records. Many CRUD servers also include a route to get all the records that are present.
These are the basic routes we’ll need:
| Method | Route | Function |
|---|---|---|
| GET | /employees |
Get all records |
| GET | /employee/<id> |
Get a single record |
| POST | /employee |
Create a record |
| PUT | /employee/<id> |
Update a record |
| DELETE | /employee/<id> |
Delete a record |
In this simple example, we don’t need to deal with data storage, as the focus will be on serving data. So we’ll use a simple in-memory solution.
Source filesystem
We’ll distribute the code over different source files, each of which will be treated as a different Rust mod. Because of this, our project’s structure will resemble the structure of a node.js or express ...