Type Aliases vs Interfaces: What’s the Key Difference?

If you find this story helpful, feel free to give it a like or share it with someone who might appreciate it too!

---

I’m a tailor in a tailor shop. Every day, customers come in with specific requests for custom-made outfits. To keep everything organized, I’ve got two tools at my disposal: type aliases and interfaces. They help me manage the different patterns and fabrics I work with.

Type aliases are like my trusty fashion catalog. When a customer wants a particular style, I flip open the catalog to a page that clearly defines that style. It might say, “A-line dress with a V-neck and short sleeves.” This catalog page is simple and straightforward, perfect for those clear-cut, no-fuss designs. I can even scribble down notes in the margins to add more details whenever I need to.

Interfaces, on the other hand, are like a set of tailor’s guidelines. They’re a bit more formal and structured. a guidebook that describes how to make a three-piece suit. It details every piece: the jacket, the vest, and the trousers. What’s unique about this guidebook is its flexibility; it allows me to add new chapters or sections as trends change or as the customer requests something extra—like an extra pocket or a different cuff style.

In my workshop, both the catalog and the guidebook are crucial. The catalog helps me quickly reference and replicate popular designs, while the guidebook ensures that when I craft something as complex as a suit, everything fits together perfectly, even if I decide to add new elements later.

So, as a tailor, I decide when to use the catalog or the guidebook based on the needs of the day. Some days, I rely heavily on the catalog for its simplicity, and other times, the guidebook’s adaptability is indispensable. In my workshop, both tools coexist, making sure every piece of clothing I create is as unique and fitting as my customers are.

---

Type Aliases

Think of type aliases as the fashion catalog. They provide a straightforward way to define a specific shape of data. For example, if I want to define a simple shape for a dress, I might use a type alias like this:

type Dress = {
  neckline: string;
  sleeveLength: string;
  length: string;
};

let summerDress: Dress = {
  neckline: "V-neck",
  sleeveLength: "short",
  length: "knee"
};

This type alias, Dress, defines a specific style, much like a catalog page. It’s straightforward and serves well for uncomplicated structures.

Interfaces

Now, let’s look at interfaces, our tailor’s guidelines. They shine when I need more structure and extensibility, like when creating a complex suit:

interface Suit {
  jacket: {
    color: string;
    buttons: number;
  };
  vest: {
    color: string;
    pockets: number;
  };
  trousers: {
    color: string;
    length: number;
  };
}

let formalSuit: Suit = {
  jacket: {
    color: "black",
    buttons: 3
  },
  vest: {
    color: "black",
    pockets: 2
  },
  trousers: {
    color: "black",
    length: 32
  }
};

Interfaces not only define the initial structure but also allow me to add additional properties in the future without altering the existing setup. I can extend them, much like adding new chapters to a guideline:

interface SuitWithTie extends Suit {
  tie: {
    color: string;
    pattern: string;
  };
}

let businessSuit: SuitWithTie = {
  jacket: {
    color: "navy",
    buttons: 2
  },
  vest: {
    color: "navy",
    pockets: 2
  },
  trousers: {
    color: "navy",
    length: 32
  },
  tie: {
    color: "red",
    pattern: "striped"
  }
};

Key Takeaways

• Type Aliases are great for defining simple, straightforward data structures. They’re like a quick reference in a fashion catalog.
• Interfaces provide a more formal and extensible way to define complex data structures. They allow for modifications and extensions, akin to adding new guidelines in a tailor’s guidebook.
• Choosing between them depends on the complexity and future-proofing needs of your data structure. For simple, static definitions, type aliases are perfect. For more complex, adaptable designs, interfaces are the way to go.