🤖 AI Summary
This study addresses the lack of systematic empirical evidence on how Rust design patterns influence code quality and compile-time invariant guarantees. For the first time in Rust backend systems, we construct an evaluation framework grounded in the SQuaRE quality model by applying the typestate and newtype patterns—combined with the “Parse, don’t validate” principle—across three representative components. Our assessment integrates benchmarking, static analysis, and expert interviews. Results demonstrate that typestate significantly enhances fault tolerance and testability, albeit potentially at the cost of readability, while newtype effectively eliminates invalid runtime states with negligible overhead, substantially improving overall software quality. This work provides the first empirical foundation for the engineering application of Rust design patterns.
📝 Abstract
Software design patterns' effects on code quality have mostly been studied in the context of object-oriented languages. In the programming language Rust, which comes with novel language concepts, compile-time safety guarantees and a distinct type system, there has been little research on design patterns. This work investigates how patterns affect software quality and compile-time enforcement of invariants through a case study on three representative components of production backend applications. An evaluation framework based on criteria derived from the SQuaRE quality model, incorporating benchmarking, static code analysis and expert interviews, is developed to assess the refactored code. The patterns typestate and newtype are applied to address existing code smells in the selected use cases. While the typestate pattern improves faultlessness and testability significantly, it comes at the cost of more structural code that can degrade readability. Code with extensive branching logic and a high number of invariants is likely to benefit most from the pattern. The newtype pattern combined with the "Parse, don't validate" principle offers high returns in software quality at a low cost and prevents invalid states during runtime. Overall, this work provides an initial empirical assessment of design patterns in Rust and establishes a foundation for further studies involving additional use cases and patterns.