TypeScript interface, type, abstract class, and Generics Compared

interface, type, and abstract class can all describe structure, but they are not interchangeable in every situation.

interface

interface is commonly used to describe object shapes, especially public APIs and class contracts.

interface User {
  id: string;
  name: string;
}
 
class Admin implements User {
  constructor(
    public id: string,
    public name: string,
  ) {}
}

Interfaces can be merged through repeated declarations, which can be useful when extending third-party types.

type

type is more flexible for unions, intersections, and complex combinations.

type Status = "idle" | "loading" | "success" | "error";
type UserWithRole = User & { role: string };

Use type for state unions, function types, and composed type logic.

abstract class

An abstract class can define both a type contract and shared implementation.

abstract class Repository<T> {
  abstract findById(id: string): Promise<T | null>;
 
  logQuery(id: string) {
    console.log(`find ${id}`);
  }
}

Use abstract classes when subclasses should share actual code.

Generics

Generics parameterize types.

function identity<T>(value: T): T {
  return value;
}
 
const name = identity<string>("Alice");

They are common in collections, API responses, and utility functions.

interface ApiResponse<T> {
  data: T;
  error?: string;
}
 
type UserResponse = ApiResponse<User>;

Simple Selection Rules

Object shape: prefer interface
Union, intersection, utility type: prefer type
Shared implementation with subclass requirements: use abstract class
Reusable type logic: use generics

Deeper Notes

When reviewing this topic, do not memorize names only. Focus on interfaces, type aliases, abstract classes, generic constraints, and public type design. If this stays at the definition level, it becomes hard to explain in interviews or apply in projects. A stronger way to study it is to place it in a concrete scenario: who calls it, where the input comes from, what happens on failure, and whether data or state can be processed twice.

TypeScript moves uncertainty from runtime to development time, but it does not replace runtime validation.
Type design should model business constraints first instead of showing off complex generics.
For third-party input, JSON, forms, and API responses, combine types with narrowing or schema validation.

In a real project, use it as a decision framework: identify inputs, constraints, failure modes, and observability before choosing a specific tool or pattern. If a solution looks simple, keep asking whether it still works when scale grows, permissions change, recovery matters, and more people collaborate on it.

Practical Checklist

Identify where this concept sits in the system: development-time constraint, runtime behavior, infrastructure capability, or collaboration workflow.
Write one minimal working example and one failure example; only knowing the happy path is usually not enough.
Record common misuses: edge cases, permission assumptions, performance assumptions, sync/async differences, or environment differences.
Connect the concept to a project experience so that an interview answer can be grounded in real tradeoffs.
End with one sentence about tradeoff: what it gives up and what it buys.

Self-Check Questions

What core problem does this topic solve?
What alternatives exist, and what are their costs?
Where are the most likely edge cases?
How would code, tests, or monitoring prove that it is reliable?

Applied Scenario

A practical scenario is a project with shared frontend/backend types. An API returns JSON; the frontend validates it with a schema, then passes the validated data into TypeScript types. Types improve editor feedback and compile-time checking, but they cannot guarantee that network data is valid. Good type design expresses business constraints such as roles, states, permissions, request parameters, and response shapes instead of turning everything into string or any.

Common Pitfalls:

Treating TypeScript types as runtime validation.
Using any for convenience and pushing errors into production.
Making generics so complex that callers cannot understand them.

Table of Contents