Avoid records for complex behavior or mutable states.
Records are not suitable for classes requiring complex business logic or mutable fields. They are designed for simple data carriers. For example, if your `Order` class needs methods beyond basic data handling, like processing or state transitions, a traditional class is more appropriate.