A programming paradigm is a fundamental style or approach to writing software — such as imperative, object-oriented, functional, or declarative — that shapes how developers structure code, model state, and reason about behavior. The paradigm a team works in influences how its APIs are designed, consumed, and evolved.
Programming Paradigm
Programming Paradigm is the underlying style or approach a developer uses to structure and express software — imperative, object-oriented, functional, declarative, event-driven, and more. A paradigm is not a language; most modern languages support several. It sets the mental model for how state is held, how logic is composed, and how a system is reasoned about, which in turn colors every interface that software exposes.
- Imperative and procedural - Code as an explicit sequence of statements that change program state step by step.
- Object-oriented - Behavior and state bundled into objects, the model behind much of the resource-oriented thinking in API design.
- Functional and declarative - Describing what should happen rather than how, favoring immutability and composition — the sensibility behind GraphQL queries and pipeline-style tooling.
- Event-driven - Reacting to messages and signals as they arrive, the paradigm underneath Pub/Sub and event-driven APIs.
Paradigms show up in API operations more than teams realize. A resource-oriented REST design reflects object-oriented habits, a GraphQL schema leans declarative and functional, and an event-driven estate reflects a reactive paradigm end to end. In the agentic turn, the declarative and functional styles matter most — agents do better when they can state a desired outcome and let tooling resolve the steps, so the paradigm a producer designs around quietly determines how easily machines can consume its APIs.
