Mastering Software Design: Why Model, Interface, and Implementation Matter

Model, Interface, Implementation

When approaching a new codebase, first identify the high‑level model, then the interface, and finally the implementation.

Model

The model is the abstract representation of the system – the core concepts and relationships.

In distributed computation, consider task scheduling across nodes.

MapReduce: define map and reduce phases.

Spark: focus on the computation, abstracting away machines.

Interface

The interface exposes the model’s capabilities.

Library APIs, e.g., Guava wrapping JDK APIs.

Command‑line tools (Unix utilities).

Business systems’ REST or RPC endpoints.

Implementation

Implementation details realize the model and interface.

Whether a request writes to a DB or forwards to another service.

Choosing existing libraries vs custom code.

Distribution vs centralization, single‑threaded vs multi‑threaded.

Resource contention handling (local vs middleware).

Protocol selection for inter‑system communication.

Case Studies

Redis

Redis added multithreading in version 6.0; the model and API remained unchanged while only the implementation was updated.

CRM System

Model elements: project, customer, contract, payment with relationships (customer → project → contract → payment). The interface manages the end‑to‑end workflow; implementation concerns messaging, state control, and deduplication.

Three‑Step Design Process

Discuss design in the order Model → Interface → Implementation . Keeping layers separate prevents mixing concerns.

Example: an architecture diagram where order, payment, logistics are model layers, while RabbitMQ is an implementation detail that can be replaced.

Reference: RocketMQ design concepts – https://github.com/apache/rocketmq/blob/master/docs/cn/concept.md

Operating‑system example: process‑management model, process creation/termination interface, scheduling algorithm implementation.

Data‑structure example: Java HashMap – model is a hash table, interface provides get / put, implementation evolved from linked‑list buckets to red‑black trees.

Summary

Model : Core abstraction that distinguishes the system.

Interface : Entry points that expose the model’s capabilities.

Implementation : Concrete techniques, languages, and frameworks that realize the model and interface.

Understanding a design proceeds from model to interface to implementation, building a mental “design tree”.