This is why databases accessed over a socket instead of being an embedded library are actually a great abstraction, not necessarily a technical one, but an organizational abstraction! During development it can be a simple container running on your developers machines, while in production it can be anything from a container running on the same server as your application, or a distributed cluster accessed through the network.

Because it's far easier to find code with the Search file feature of your code editor when it's in a descriptive filename (client.rs, email.rs, payments.rs...) than if everything is stashed in 10 different mod.rs or lib.rs files.

A simple mark initiative, similar to "Made by humans" and other badges

A thin HTTP API interface pattern.

This is what we often build in UIs with JS to interface with backends.

A faster implementation of the rust datetime library

A rust example project using SQLx and sqlite.

Read the pp_dataserver later to learn how to use Axum with a SQLite database.

Great FAQ 😄

Didn't read, but it can be useful someday

A lightweight version of the builder pattern

An introduction to IRC

Un exemple de passage de RSA aux courbes elliptiques (ici P-256 avec l'algorithme Ed25519)

The five CUPID properties:

• Composable: plays well with others
• Unix philosophy: does one thing well
• Predictable: does what you expect
• Idiomatic: feels natural
• Domain-based: the code models the problem domain in language and structur