Scribd
Upload
23 views2 pages

Understanding Application Programming Interfaces

Uploaded by

Michael
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
23 views2 pages

Understanding Application Programming Interfaces

Uploaded by

Michael
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd

APPLICATION PROGRAMMING INTERFACE(API)

An application programming interface (API) is a way for two or more computer programs or
components to communicate with each other. It is a type of software interface, offering a service to
other pieces of software. A document or standard that describes how to build or use such a
connection or interface is called an API specification. A computer system that meets this standard is
said to implement or expose an API. The term API may refer either to the specification or to the
implementation. Whereas a system’s user interface dictates how its end-users interact with the
system in question, its API dictates how to write code that takes advantage of that system’s
capabilities.

In contrast to a user interface, which connects a computer to a person, an application programming


interface connects computers or pieces of software to each other. It is not intended to be used
directly by a person (the end user) other than a computer programmer who is incorporating it into the
software. An API is often made up of different parts which act as tools or services that are available to
the programmer. A program or a programmer that uses one of these parts is said to call that portion
of the API. The calls that make up the API are also known as subroutines, methods, requests, or
endpoints. An API specification defines these calls, meaning that it explains how to use or implement
them.

One purpose of APIs is to hide the internal details of how a system works, exposing only those parts
that a programmer will find useful, and keeping them consistent even if the internal details change
later. An API may be custom-built for a particular pair of systems, or it may be a shared standard
allowing interoperability among many systems.

There are APIs for programming languages, software libraries, computer operating systems, and
computer hardware. APIs originated in the 1940s, though the term did not emerge until the 1960s and
1970s. Contemporary usage of the term API often refers to web APIs, which allow communication
between computers that are joined by the internet. Recent developments in APIs have led to the rise
in popularity of micro services, which are loosely coupled services accessed through public APIs.

APIs should be versioned. There are two common versioning strategies:

➢ Additive change strategy: new features are added without modifying existing ones. Any
update must be backward compatible. This strategy is suitable for small projects with low rate
of change.
➢ Explicit version strategy: this strategy allows making any changes including breaking changes.
This strategy is suitable for complex applications and complex changes.

Purpose
In building applications, an API simplifies programming by abstracting the underlying implementation
and only exposing objects or actions the developer needs. While a graphical interface for an email
client might provide a user with a button that performs all the steps for fetching and highlighting new
emails, an API for file input/output might give the developer a function that copies a file from one
location to another without requiring that the developer understand the file system operations
occurring behind the scenes.

Common questions

Powered by AI

A user interface is designed for end-users, facilitating direct interaction with the system via elements like buttons and forms. In contrast, an API is designed for computer programs and developers, enabling software components to communicate by exposing only necessary functionalities without human intervention in the process. The API focuses on programmatic interaction rather than user-centric design .

An API facilitates communication between programs by providing a set of defined methods, known as calls, such as subroutines, requests, or endpoints. The API specification documents how these calls should be implemented and used. It hides the complexity of underlying processes and exposes only the parts necessary for communication, making programming simpler by abstracting implementation details .

APIs abstract complex operations by providing simple, well-defined methods that encapsulate complicated procedures, such as file transfers, without exposing the underlying processes. This abstraction reduces the developer's need to understand intricate system details, allowing them to focus on building functionality. It enhances productivity, reduces errors, and facilitates easier integration of capabilities into new applications .

APIs originated in the 1940s and evolved through the 1960s and 1970s. The term 'API' emerged as computing systems required standardized ways to allow software components to interact. The advent of the internet and web technologies led to current web APIs, which are crucial for modern, interconnected systems enabling global communication and service integration at an unprecedented scale .

APIs protect a system's internal workings by implementing an abstraction layer that hides complex system intricacies and exposes only the methods necessary for external interaction. This layer acts as a barrier, allowing controlled access to system functionalities, which helps maintain security and stability while enabling interoperability and ease of use for developers .

The primary purposes of an API in software development are to simplify programming by abstracting the underlying implementation, exposing only the necessary objects or actions for developers, and enabling interoperability between different software systems. This abstraction allows developers to use functionalities without needing to understand the internal workings of the system .

A custom-built API is more advantageous in scenarios requiring tailored solutions for specific system pairs, ensuring high efficiency and performance optimizations tailored to particular use cases. It provides targeted functionality and control over system interactions that a shared standard API may not offer, making it ideal for specialized environments or applications with unique requirements .

Modern web APIs contribute to the rise of microservices by providing lightweight, standardized communication methods over the internet that allow independently deployable services to interact seamlessly. They enable the loose coupling of services, which is essential for the scalable and flexible architecture that characterizes microservices. This modular approach benefits agile development, allowing frequent updates and service scalability without affecting the entire system .

APIs significantly enhance software interoperability by providing standardized interfaces that different systems and programming languages can implement and understand. This standardization allows diverse systems to communicate regardless of underlying architectures or technologies, supporting integration and innovation across various platforms. APIs facilitate cross-platform development, decrease redundancy, and enhance the versatility of software applications .

API versioning strategies differ mainly in their approaches to changes and compatibility. The additive change strategy incorporates new features without altering existing ones, ensuring backward compatibility, suitable for projects with a low change rate. The explicit version strategy allows any changes, including breaking ones, and is suitable for complex applications needing significant updates. Each strategy intends to manage changes while ensuring system interoperability and reliability .

You might also like