Use records when modeling simple, immutable data carriers.
Records are best suited for plain data carriers with no complex behavior. Consider an `Address` record with fields like `street` and `city`. It's a simple, immutable structure where records shine, unlike a `Customer` class which might require complex logic.
Additional Notes
When might you choose records over classes for data modeling?