Let's try to know more about Pub/Sub design pattern and learn some facts about it.
π§΅ππ»
Publish/Subscribe (Pub/Sub) is an asynchronous messaging style used in serverless and microservices architectures.
With this model, messages are not sent to a specific subscriber but are instead categorized to be available to all subscribers of the category.
π How Pub/Sub Pattern Based APIs Work
The main characteristic of Pub/Sub APIs is the existence of publishers and subscribers, as the name implies. Publishers categorize messages and those that are subscribed to a specified category receive that message.
Kafka APIs are considered to be a type of Pub/Sub based APIs. Other types of APIs and microservices can also be built around a Pub/Sub system, including REST APIs.
For example, REST APIs use POST and DELETE operations to integrate with Pub/Sub.
β‘οΈ POST operations publish messages and create subscriptions.
β‘οΈ DELETE is used to unsubscribe.
π When to Use Pub/Sub Pattern Based APIs
πΉ Pub/Sub based APIs are a great addition to architecture systems that involve many independent or decoupled components.
πΉ Pub/Sub based APIs can be used to provide event-driven notifications as a result of specific events that occur within the system. This style of system is also highly scalable compared to more traditional client-server infrastructure.
π Maturity of Pub/Sub Pattern Based APIs
Pub/Sub systems have been around since the late 1980s. However, Pub/Sub systems and Pub/Sub-based APIs also have more modern implementations.
One of the most notable is the Cloud Pub/Sub by Google Cloud. Based on this, we believe Pub/Sub-based APIs are here to stay, and these systems may inspire new types of APIs β like Kafka.
With that being said, this is the end of this thread.
Head over to RapidAPI Hub (RapidAPI.com/hub?utm_sourceβ¦) and explore tens of thousands of excellent APIs you can use with a single API Key. π
β’ β’ β’
Missing some Tweet in this thread? You can try to
force a refresh
- This API provides sentiment analysis, stemming and lemmatization, part-of-speech tagging and chunking, phrase extraction, and named entity recognition.
API testing is performed to test whether a particular API meets some pre-defined parameters or not.
Let's talk more about API Testing π§΅ππ»
API testing includes testing APIs in isolation to ascertain if they meet the functionality, reliability, latency, performance, security, and other essential parameters.
API testing commonly includes testing APIs with JSON or XML payload sent over HTTP, HTTPS, JMS, and MQ. These are widely used data formats and networking/messaging protocols.
There are three main characteristics of HTTP Request Methods:
1. Safe 2. Idempotent 3. Cacheable
Let's talk about them in this thread. π§΅ππ»
πΈ Safe
We can call an HTTP request method safe if it doesn't affect the server's state.
The safe methods request the server to send data without performing any modification to the original data. Hence safe methods accomplish read-only operations.
Even though they are read-only operations, they sometimes cause a change in server state; the server can update its statistics.
One thing to note here is that the safe methods never request the server to change its state.