liveBook · Manning

Port

As explained in Acing the Frontend Interview

A port is an interface defining a communication boundary through which an application exposes capabilities or accesses an external dependency.

A port is an interface defining a communication boundary: an application exposes capabilities through inbound ports or accesses external dependencies through outbound ports. This boundary keeps communication explicit while allowing architectural layers to remain separated. section 6.1

A practical web example is a frontend request routed through an API proxy. The React application calls a local path, while Vite forwards it to the external API, hiding the backend URL and avoiding development-time CORS problems. section 6.1

Interview points to articulate:

  • Treat the port as the stable boundary and vary the implementation behind it. section 6.1

How Acing the Frontend Interview covers it

How deep it goes
Defines ports and names inbound and outbound forms, then demonstrates adjacent proxy mechanics without detailing port implementation.
Examples
Uses a React fetch call, Vite proxy configuration, Express CORS headers, and curl preflight output.
What it assumes
Assumes frontend, backend, browser security, and layered architecture fundamentals while making CORS and proxy behavior concrete.
What you can do after
Apply it via a named tool or library by explaining and configuring Vite proxy communication between frontend and external API.
How it connects
Connects ports to n-tier architecture, API proxies, CORS, same-origin policy, and layered separation of concerns.

Also explained in

Compare how 6 books explain port →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Acing the Frontend Interview. The section links point to the parts of the book it draws on.