An API gateway is a service that sits in front of a set of APIs as a single entry point. It routes requests and handles shared concerns such as authentication, rate limiting, logging and transformation.
API security is the practice of protecting application programming interfaces from misuse. It controls who can call them, what data they can reach and how much they can request.
A load balancer is a network component that spreads incoming requests across several servers or containers. It keeps any single instance from being overloaded and steers traffic away from unhealthy ones.
Microservices is an architectural style in which an application is built as a set of small, independently deployable services. Each owns a specific business capability and its own data, and talks to the others over the network.
Rate limiting is a technique that controls how many requests a client can make to a service within a set period of time. It protects systems from overload, abuse and runaway costs.
An API (application programming interface) is a defined contract that lets one piece of software request data or actions from another. It hides internal details behind agreed operations, inputs and responses.
A monolith ships the whole application as one deployable artefact; microservices split it into small services that are released independently. Monoliths are simpler early on, while microservices suit large teams that need to move separately.
A clear proven process, that delivers
You've seen our ideas - now go deeper.
Discover more insights, guides, and engineering practice.