Book Image

Rust Programming Cookbook

By : Claus Matzinger
Book Image

Rust Programming Cookbook

By: Claus Matzinger

Overview of this book

Rust 2018, Rust's first major milestone since version 1.0, brings more advancement in the Rust language. The Rust Programming Cookbook is a practical guide to help you overcome challenges when writing Rust code. This Rust book covers recipes for configuring Rust for different environments and architectural designs, and provides solutions to practical problems. It will also take you through Rust's core concepts, enabling you to create efficient, high-performance applications that use features such as zero-cost abstractions and improved memory management. As you progress, you'll delve into more advanced topics, including channels and actors, for building scalable, production-grade applications, and even get to grips with error handling, macros, and modularization to write maintainable code. You will then learn how to overcome common roadblocks when using Rust for systems programming, IoT, web development, and network programming. Finally, you'll discover what Rust 2018 has to offer for embedded programmers. By the end of the book, you'll have learned how to build fast and safe applications and services using Rust.
Table of Contents (12 chapters)

Using an ORM to save data to a database

Opinions about object-relational mappers vary considerably: their use was strongly encouraged when SQL databases stored all of the World's data but they quickly fell out of favor when it was actually the whole World's data. Typically these frameworks provide a trade-off between ease of use, language integration, and scalability. While it's true that querying terabytes of data requires a fundamentally different approach, simple CRUD-type business applications work well with frameworks that do the heavy lifting for you and—most importantly—are somewhat independent of the actual database they connect to. Rust's macros come in very handy here—they allow the ORM framework to do these things largely at compile time, so it's memory-safe, type-safe, and fast. Let's see how it's done.

...