Let's discuss the most commonly heard terms in API development ππ»
- SDK
- RPC
- CORS
- Async API
- Internal API
- API Caching
- External API
- HTTP cookies
- Authorization
- Microservices
- OpenAPI spec
- Composite API
- API Versioning
- Authentication
Thread π§΅ππ»
π SDK
SDK stands for Software Development Kit.
It is a set of development tools that allows the creation of software or an application for a particular platform.
SDK provides you with the whole package from compilers to debuggers to even a software development framework.
π RPC
Remote Procedure Call (RPC) is the oldest client-server communication method in use today. Instead of the traditional HTTP call, RPC uses a function call.
It means that on the client-side, you invoke a function that is written on the server-side code.
π CORS
CORS is an HTTP-based mechanism that lets you request data from one URL to a different URL.
Check out this note for more details: ππ»
π Async API
AsyncAPI is an open-source project aimed at improving the current state of Event-Driven Architecture.
These APIs allow relatively time-consuming requests to be processed in the background while other requests are made.
π Internal API
Internal API, also known as Private API is only accessible to the developers within an organization.
π API Caching
API Caching is the ability to store copies of frequently accessed data in several places along the request-response path.
π External API
External API, also known as Public API is accessible to all the developers outside the enterprise or organization.
π HTTP cookies
An HTTP cookie is a small piece of data created by the web server inside your browser.
The data inside a cookie has an ID that is unique to you and your computer. This ID helps the server to know who the user is so it can send the data accordingly.
π Authorization
Authorization always comes after authentication. It is the process of permitting users to access different resources from the server, and itβs not visible and changeable by the user.
π Microservices
A microservice is an application design that breaks up a monolithic architecture into small, self-containing services.
π OpenAPI spec
It is a format to define structure and syntax for REST APIs. It provides a standard that allows both humans and computers to discover and understand the service's capabilities without access to source code, documentation, or traffic inspection.
π Composite API
Composite API is a design approach in which we bundle multiple API requests into a single API call.
π API Versioning
API versioning is the practice of managing changes in your API.
You should version your API if you are introducing any breaking changes. This way, clients can still access the old version, and their products will not break as soon as you launch a new release.
π Authentication
Authentication and authorization are the two most confusing terms.
Authentication is validating the user to identify if they are who they claim to be.
β’ β’ β’
Missing some Tweet in this thread? You can try to
force a refresh
There are different kinds of specifications available that you can use while building an API.
In this thread, we will talk about the OpenAPI spec.
𧡠ππ»
In simple terms, OpenAPI spec is a format to define structure and syntax for REST APIs.
OpenAPI spec provides a standard that allows both humans and computers to discover and understand the service's capabilities without access to source code, documentation, or traffic inspection