Technical Lead in the company Proxify
The back-end is the server’s code that gets the clients’ requests and sends the necessary data back. It also includes the application’s database that stores all the information.
HTTP and REST guarantee the request-respond cycle’s structure between servers and clients.
Basically, the back-end receives the incoming request, interprets it, and sends the final response to the user. The back-end can be divided into three parts:
The server is a simple computer that catches the requests that are addressed to it. All computers can be connected to one network and behave like a simple server. If you are a developer, your computer is already a server. Note, that there are special computers that were made for receiving requests, but a regular computer will also work great.
Any application runs on the logic that dictates how to answer any request that is based on a simple HTTP verb and URI which stands for Uniform Resource Identifier. When HTTP and URI stand together, they are called a route. The matching request is called routing.
Some functions are cross-platform software. Such code runs between the request-receiving service and a response-sending request. The functions of the cross-platform software will change an object that is requested, a query of the database, or process the request. As soon as such cross-platform software passes the control to the next function of the cross-platform software it ends and doesn’t send the response.
When a function of a cross-platform software is called, then the request-respond cycle is ended. The client gets an HTTP response.
The logic of routing can be simplified with the help of the Ruby framework or Express framework. Many coders use these frameworks during their work. One of many routes can have functions of a handler that run just when the HTTP and URI routes are matched!
All data comes in many different forms when it hits the user. Just imagine you’ve sent a request and a server sends back an HTML file with JSON data. And your neighbor sent a request and got an HTTP status code. In any case, you’ve got the desired information. And you might be familiar with the «404. Not Found» page. That’s the answer to your request! However, there are many more mistakes that a server can send you back.
Databases are crucial when it comes to the back-end of any web application. They provide a memory slot to save particular data. Such a concept alleviates the CPU memory’s load and gives the opportunity to restore data if the server dies or crashes at once. Also, a client might send data with the urge to appear on the database.
When software components need to communicate, they use API which is a methods’ collection for such communication. Also, there is a Web API which is the back-end created interface.
Request types can be defined by Web API and it is defined by the routes. Such routes provide users with an expected answer.
Web API provides a user with the data without being specific on how the data is displayed. Several HTML pages and mobile apps can be developed to check the Web API data.
Map the request out!
Let’s imagine a real-life situation.
And this is how the back-end works! Basically, a user sends a request via
servers and gets a response from the closest one!
Create your free account to unlock your custom reading experience.