One of the most important qualities of our application is that the return of our endpoints is related to the correspondi

One of the daily discussions that I come across regarding various API developments is deciding whether to use singular or plural for the construction of endpoints. In short, we want to maintain a solid consistency in our application, and for this, my recommendation is to build the endpoints in plural.

It is important to know the existing status codes and know which case we need to apply each one of them, since it may happen (and it’s very common) that the return message is incorrectly associated with some status code, which is extremely harmful for the application since it generates confusion for developers and consumer users of our REST API.

Examples: It is very important to provide examples of how we can consume our interface, even if it is a bash script that we can execute in the console and get a response from it.

Resources will not always have a single result, a table can have many results and even if it had only one, and we place it singular, we will not maintain consistency in the format of the name of our routes.

One of the best ways — if not the best way — of improving at coding is to spend as much time coding as possible. The more projects and experience you have under your coding belt, the better you become.

http://molos.bodasturias.com/qxz/Video-AEK-Athens-Hapoel-Unet-Holon-v-en-gb-hxr-.php

http://elta.actiup.com/cqn/video-iokerit-v-khk-sochi-v-ru-ru-1mbh-7.php

http://www.ectp.org/kzz/videos-tecnyconta-zaragoza-v-nizhnii-novgorod-v-ru-ru-1tjn-16.php

http://team.vidrio.org/xpy/Video-tychy-v-torun-hsa-v-pl-pl-1rwm-22.php

http://molos.bodasturias.com/qxz/videos-AEK-Athens-Hapoel-Unet-Holon-v-en-gb-rpp30122020-.php

http://www.ectp.org/kzz/v-ideos-tecnyconta-zaragoza-v-nizhnii-novgorod-v-ru-ru-1aaa-4.php

http://old.cocir.org/media/qas/Video-lulea-v-rogle-v-sw-sw-1rjr-26.php

http://startup.munich.es/dyn/Video-Rauman-Lukko-Mikkelin-Jukurit-v-en-gb-1nlr30122020-12.php

http://elta.actiup.com/cqn/Video-iokerit-v-khk-sochi-v-ru-ru-1quw-20.php

http://molos.bodasturias.com/qxz/videos-AEK-Athens-Hapoel-Unet-Holon-v-en-gb-sbw-.php

fe was in medical school, we took another look at my records and discovered that I had been diagnosed, but because of the way diagnoses are created, no one had noticed. For some reason, a rheumatologist at Cleveland Clinic had tested me for a rare genetic disorder called Muckle-Wells. It’s caused by a defect on a gene responsible for the inflammatory response, the same set of genes involved in disorders like familial Mediterranean fever. I tested heterozygous, which means that I have only one bad copy of the gene, one error. At that time, a diagnosis of Muckle-Wells required a homozygous result — both copies must be defective. But the diagnostic criteria changed about a year after I left the clinic.

As we develop, it is inevitable to have a stable and definitive version of our API, without errors, and bulletproof. Let’s imagine we deploy our API and several clients are starting to use it, what would happen at some point when you need to add or remove more data from a resource? Possibly you generate a bug on the external services that consume our interface. That is why it is essential to have a versioning mechanism for our application.

One of the powerful tools that will enhance an API in speed and low resource consumption is caching, the idea is not to ask your database for the same request multiple times if it continues to have the same result. There are several services that can help us implement this system, among them, one of my favorites is Redis.

Accessibility: The location and access of the interface are one of the most important qualities, and we do not want to give a how_to_use.txt to customers. Exposing our documentation on the cloud where everyone can see it, is the most convenient thing we can do.

We have surely heard that implementing a cached functionality generally comes with costs, and this is not the exception. Let us ask the following questions, is the information dynamic or is it static? If it’s dynamic, how often does the information change?

One of our best weapons and most hated by many people is documentation. In this context, a documented API is essential so that our users who consume it can understand several important aspects of our interface, including accessibility, responses, requests, examples.

Remember that our API is the interface that we expose to consume our back end service, with this in mind, it is important to apply the best possible principles so that the people who consume and work on it, are to their liking.

Speaking of consistency, if we know that a route is responsible for handling the actions on a resource, it is essential to name it with the name of the resource directly, so when a person consumes our API, they will understand which entities they are working on.

Many cases in any application that consumes our API, will want, in some way, to consume fewer resources from our service, either due to performance, a search system, the information is excessive, or as simple as showing something particular from our resources.

These ways are valid and I have seen them in many projects. Personally, I consider it cleaner to use a query string than expanding the current path. The more the application scales, we will surely have a greater hierarchy and in turn, the route will expand. Even so, it is according to the criteria of each person, so use the one you prefer the most!