Application Programming Interface (API): Difference between revisions

From GM-RKB
Jump to navigation Jump to search
No edit summary
Line 7: Line 7:
** It can (typically) handle [[API Version]] through [[version strategy]].
** It can (typically) handle [[API Version]] through [[version strategy]].
** It can (typically) support [[API Documentation]] via [[interface description]].
** It can (typically) support [[API Documentation]] via [[interface description]].
** ...
** It can (typically) measure [[API Performance]] through [[performance metric]]s.
** It can (typically) implement [[API Error Handling]] through [[error response]]s.
** It can (typically) manage [[API Lifecycle]] through [[lifecycle phase]]s.
** It can (typically) enable [[Cross-Platform Integration]] through [[platform-agnostic protocol]]s.
** It can (typically) collect [[API Analytics]] through [[monitoring system]]s.
** It can (often) be specified by an [[API Specification]], which describes its functionalities, methods, and data formats.
** It can (often) be specified by an [[API Specification]], which describes its functionalities, methods, and data formats.
** It can (often) be tested via an [[API Testing Task]] (often a [[component test]]).
** It can (often) be tested via an [[API Testing Task]] (often a [[component test]]).
Line 13: Line 17:
** It can (often) enable [[system interoperability]] through [[standard protocol]]s.
** It can (often) enable [[system interoperability]] through [[standard protocol]]s.
** It can (often) provide [[backward compatibility]] using [[version control]].
** It can (often) provide [[backward compatibility]] using [[version control]].
** It can (often) optimize [[API Response Time]] via [[caching strategy]].
** It can (often) provide [[API Status Code]] for [[error classification]].
** It can (often) support [[API Deprecation]] via [[sunset policy]].
** It can (often) support [[Multiple Client Language]]s via [[language binding]]s.
** It can (often) track [[API Usage Pattern]]s via [[usage metric]]s.
** ...
** ...
** It can range from being a [[Simple API]] to being a [[Complex API]], depending on its [[functionality scope]].
** It can range from being a [[Simple API]] to being a [[Complex API]], depending on its [[functionality scope]].
Line 18: Line 27:
** It can range from being a [[Synchronous API]] to being an [[Asynchronous API]] (that implements [[API callback]]s), depending on its [[interaction pattern]].
** It can range from being a [[Synchronous API]] to being an [[Asynchronous API]] (that implements [[API callback]]s), depending on its [[interaction pattern]].
** It can range from being a [[Monolithic API]] to being a [[Microservice API]], depending on its [[architectural style]].
** It can range from being a [[Monolithic API]] to being a [[Microservice API]], depending on its [[architectural style]].
** It can range from being a [[Low-Latency API]] to being a [[High-Throughput API]], depending on its [[performance requirement]]s.
** It can range from being a [[Basic Error Handler]] to being a [[Comprehensive Error Handler]], depending on its [[error handling strategy]].
** It can range from being an [[Experimental API]] to being a [[Production API]], depending on its [[maturity level]].
** It can range from being a [[Platform-Specific API]] to being a [[Universal API]], depending on its [[platform support]].
** It can range from being a [[Basic Monitored API]] to being an [[Advanced Monitored API]], depending on its [[monitoring capability]].
** ...
** ...
** It can utilize mechanisms like [[Webhooks]], [[WebSockets]], [[Server-Sent Events (SSE)]], and [[Message Queues]] for [[asynchronous communication]].
** It can utilize mechanisms like [[Webhooks]], [[WebSockets]], [[Server-Sent Events (SSE)]], and [[Message Queues]] for [[asynchronous communication]].

Revision as of 23:25, 30 December 2024

An Application Programming Interface (API) is a computing system interface that can be used for building a software application (through standardized program interaction and component communication).



References

2024-12-30

[1] https://www.ibm.com/think/topics/api
[2] https://en.wikipedia.org/wiki/Api
[3] https://blog.postman.com/top-30-apis-for-best-developer-experience/
[4] https://blog.dreamfactory.com/6-examples-of-apis-we-use-in-our-everyday-lives
[5] https://aws.amazon.com/what-is/api/
[6] https://katalon.com/resources-center/blog/api-examples
[7] https://www.techtarget.com/searchapparchitecture/definition/application-program-interface-API
[8] https://www.talend.com/resources/what-is-an-api/
[9] https://www.mulesoft.com/api/what-is-an-api
[10] https://www.altexsoft.com/blog/what-is-api-definition-types-specifications-documentation/

2024

  • (Wikipedia, 2024) ⇒ https://en.wikipedia.org/wiki/API Retrieved:2024-6-20.
    • An () 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 . A computer system that meets this standard is said to or 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 that portion of the API. The calls that make up the API are also known as subroutines, methods, requests, or endpoints. An API specification 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,[1] which allow communication between computers that are joined by the internet. Recent developments in APIs have led to the rise in popularity of microservices, 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.
  1. Cite error: Invalid <ref> tag; no text was provided for refs named Lane2019

2016

  • (Wikipedia, 2016) ⇒ http://wikipedia.org/wiki/Application_programming_interface Retrieved:2016-4-29.
    • In computer programming, an application programming interface (API) is a set of routines, protocols, and tools for building software and applications.

      An API expresses a software component in terms of its operations, inputs, outputs, and underlying types, defining functionalities that are independent of their respective implementations, which allows definitions and implementations to vary without compromising the interface. A good API makes it easier to develop a program by providing all the building blocks, which are then put together by the programmer. ...