Commonly confused

HTTP vs API Gateway

HTTP is the protocol. An API gateway is a control point that accepts HTTP API calls with policy on top.

HTTP

HTTP, or Hypertext Transfer Protocol, is a foundational network protocol used for transmitting hypermedia documents, such as HTML, across the internet. It defines how messages are formatted and transmitted, and what actions web servers and browsers should take in response to.

HTTP is the internet's primary protocol for transferring web pages and other hypermedia documents between clients and servers.

Full PathTerms™ definition

API Gateway

An API Gateway is a server that acts as a single entry point for clients accessing various backend services. It handles incoming requests, routes them to the appropriate microservice or application, and then returns the response to the client. This abstraction simplifies client.

An API Gateway is a single entry point for clients accessing backend services, simplifying interactions and centralizing management.

Full PathTerms™ definition

Why it matters

People mix up HTTP and API Gateway in exam questions and job posts. Knowing the difference helps you pick the right control, process, or architecture choice.

How to remember the difference

HTTP is the protocol. An API gateway is a control point that accepts HTTP API calls with policy on top.

Related exam lists