🏗️

Constructor

FoundationsThe routine that establishes initial object state

A constructor is the routine that runs when an object is being created and brings it into a usable starting state. It gathers the rules for which values are required and which invariants must hold from the very beginning.

▶Architecture Diagram

🔄 Process

📦Allocate Memory

🏗️Constructor

✅Default Invariants

🔌Dependencies

📦Usable Object

Dashed line animations indicate the flow direction of data or requests

Why do you need it?

If an object is created first and configured later in many places, partially initialized instances can leak into the program. Bugs then appear far away from the creation site because methods are called before the object is truly ready.

Why did this approach emerge?

As classes accumulated more dependencies and more initialization rules, safe construction became a first-class concern. Object-oriented languages therefore made room for a dedicated creation-time hook so valid initial state could be established explicitly.

How does it work inside?

Typically the runtime allocates memory for the new instance and then calls the constructor. The constructor receives arguments, fills fields, applies defaults, and only after that can the object be treated as ready for normal method calls.

Boundaries & Distinctions

Constructors and factory methods both deal with object creation, but they emphasize different concerns. The constructor is the direct path for initializing one class, while a factory method is more useful when choosing among concrete types or wrapping a larger creation process.

When should you use it?

Constructors matter for service objects with required collaborators, domain objects that must start in a valid state, and infrastructure objects that need configuration before use. If too many optional branches or creation modes accumulate, a single constructor can become hard to read and too responsible.

Enforce required values -- inject mandatory dependencies and fields at creation timeProtect invariants -- block objects from being born in an invalid stateCentralize initialization -- gather scattered setup logic into one entry pointConnect collaborators -- wire needed services and configuration when the object is created