Do you use nouns for class names?

What is a noun?

A noun is a word that names a thing. Common examples include tangible items like table, cup, or computer; and abstract entities like record, database, or cloud.

Naming classes as nouns

In your code, class names should clearly reflect what they represent, giving developers an immediate understanding of the class’s role.

❌ Figure: Bad example - This name suggests an action which sounds like it could be a method - but it's meant to represent the order itself

✅ Figure: Good example - A class name that clearly represents a thing is much easier to understand - you couldn't misinterpret this as a method

Later, if you need to perform an action on the order, you might create a ProcessOrder method within theOrderService or OrderProcessor class (see our rule Do you use verbs for method names?)

Events: The exception that proves the rule

In domain-driven design (DDD) and event-driven architectures (EDA), you’ll often see exceptions to this rule. Events like OrderPlaced or UserRegistered are commonly named with verb phrases to represent specific actions or occurrences within the system, rather than entities with persistent state. This naming convention is acceptable, as it indicates a change or trigger rather than a static object. For other class types, however, sticking to nouns keeps the codebase clear and consistent.