Adapter Pattern

Converts the interface of one class into the interface another class expects, making incompatible interfaces work together.

#structural#adapter#compatibility

Field Note - Real-world Analogy

Think of it like this

“Like a travel power adapter. Your laptop has a US two-pin plug, but the hotel wall socket in Europe is different. The adapter is a small piece that goes between them — your laptop is unchanged, the wall is unchanged, and the adapter makes them compatible.”

Field Observations - Key Topics Covered

The problem: you have code that uses an interface (e.g., it calls .read() and .write()) but the library or service you want to use has a completely different interface (e.g., .fetch() and .push()). You can't change either side — maybe it's a third-party library or legacy code.

4 more observations inside

Unlock Full Note

Ready to go deeper?

Open the complete revision note.

Sign in to read every field observation in full, including a runnable code example and side-by-side comparisons with related patterns.

Read Full Notes