Importance of proper Request Handling

In this article

  1. SPA
A Number of network requests grows rapidly and it is important to pick a proper way to handle them. Let’s check the most popular approaches.

SPA

Any service that gets incoming requests has to handle them and, most often, return some kind of response. Such a service can be either a service that handles tasks in a database or a service that handles requests over a network.

According to the Internet live stats, there are about 2 billion web services so far and the number of them is growing every minute. So, the number of network requests and data that should be handled, are also rapidly increasing.

Each method of network request handling has its own positive and negative sides. Therefore, the performance, speed, and operability of your application depend on the choice of approach for handling such requests.

A lot of articles consider how to handle synchronous and asynchronous network requests only partially. That's why we would like to describe the most widespread approaches to this process.

Synchronous approaches:

Probably the simplest synchronous approach to handling network requests is "Sequential handling of requests". But the lack of parallelism in request handling creates a natural queue, which makes scaling impossible. As a result, using this approach a large number of data can't be handled in a timely manner.

With a "Process for a request" architecture, an application consists of main and work processes. The main process handles incoming requests and creates a work process for each new request. In this case, scaling is the simplest, but the process consumes a lot of resources, and the absence (by default) of shared memory does not allow to have access to shared data.

At the same time, the work processes are independent of each other, and errors in one process do not affect the work of other work processes. Access rights are managed by standard OS mechanisms, and for changing the request handling algorithm the only thing you have to do is to change the script. Probably the best DBMS to handle such requests is PostgreSQL, which will make it possible to effectively use multi-core CPUs.

"Thread for a request" is also simple to implement and resembles the previous approach, except using of threads. In this case, it is possible to have shared memory and effectively use multi-core CPUs. But unfortunately, this approach is more resource intensive.

"Processes/threads pool" is a mixed approach that is difficult to implement and is quite expensive at cost. The main thread accepts incoming requests and builds them in a queue, which is handled by work processes. In this way, scaling is performed, but it is limited in conjunction with the resources used. At the same time, resources are more spent on creating a pool, which reduces costs while creating separated threads or processes and effectively uses multi-core CPUs.

Asynchronous approaches:

Asynchronous handling of all requests is typical for event-oriented handling - "Reactor pattern". Such handling consists of multiple calls followed by handlers. In a single-threaded application, only one handler is executed, while in an application that uses the "Reactor pattern" approach, handlers are pseudo-parallel.

This approach allows you to scale efficiently no-CPU-intensive requests and the number of connections, which will significantly increase application performance. "Reactor pattern" is quite difficult to implement and the occurrence of errors will lead to complete blocking of the service.

In the approach "Half sync/half async", a simplified (green) control thread is used. There are other threads in the application controlled at the OS level, but green threads are managed by the application execution system. In this case, the performance of the asynchronous approach is combined with the simplicity of programming the synchronous code.

With proper implementation of the approach, requests and the number of simultaneous connections could be well scaled. The code with the approach is easier to develop than code with other asynchronous approaches. However, errors that occurred and the handling time of requests can block the entire process, which is especially bad for real-time systems.

"Pipelining" is the handling process with a chain of several OS threads. Each thread at each moment of time performs a set of operations to handle the request.

This approach is well scaled, but unfortunately, it is not suitable for some types of network requests. Moreover, this approach is quite difficult to implement and test.

This article describes only the most frequently used approaches for network request handling and you could hear about other ones. However, more pros and cons for each method can be found in a specific situations and in specific application.

Blog

ionic-vs-electron image

Ionic vs Electron: Mobile or Desktop Development

This article delves into the comparative analysis of the Electron vs Ionic frameworks, exploring their unique characteristics, strengths, and ideal use cases.

Apr 09, 2024
it-staff-augmentation-vs-outsourcing image

Staff Augmentation vs Project Outsourcing: What is the Difference and How to Choose?

In today`s business environment, companies actively use various models of working with personnel to optimize costs and increase efficiency. Staff augmentation and outsourcing are two of the most popular formats of cooperation. Both approaches offer companies various advantages: access to professional IT specialists, reduced staffing costs, and increased operational flexibility. Choosing an outsourcing or staff augmentation model depends on many factors, including project specifics, budget, timing, and skill requirements.

Mar 26, 2024
outsourcing-vs-outstaffing image

Outsourcing vs. Outstaffing: Which Model Will Suit For Your Business?

One of the important tasks of any business or project is to optimize processes that will allow you to perform valuable actions without unnecessary effort. This applies to software development: applications, websites, or mobile apps, etc. In most cases, such work is project-based and does not require a permanent employee on staff. That is why outsourcing and outstaffing services are optimal.

Mar 15, 2024
chatbot-development-everything-you-need-to-know image

Chatbot Development: Everything You Need To Know

The journey of bots commenced in 1966 with the emergence of text bots like Eliza, progressing into voice-based bots during the 80s. Simply put, a bot is software capable of engaging in intelligent conversations with humans.

Feb 12, 2024
10-backend-development-trends-to-follow-in-2024 image

10 Backend Development Trends to Follow in 2024

Backend development serves as the foundational structure for websites and applications, driving the functionality and performance upon which users depend. The backend development landscape is constantly evolving, propelled by emerging technologies and evolving digital business practices.

Jan 09, 2024
angular-v17 image

Angular v17: What Is Our MaybeWorks Team Impressed Most Of All?

Celebrating the 13th milestone of Angular's iconic red shield, the Angular team reflects on the legacy of AngularJS as the catalyst for a revolutionary era in JavaScript frameworks designed to meet the escalating demand for dynamic web experiences. Now, embarking on a visionary journey with Version 17, the Angular team redefines benchmarks for performance and elevates the developer experience.

Dec 24, 2023
an-introduction-to-the-bun-javascript-runtime image

An Introduction to the Bun JavaScript Runtime

JavaScript continues to stand as the cornerstone of modern programming languages. Amidst this ever-evolving landscape, a new player has emerged — the Bun JavaScript Runtime. This groundbreaking runtime environment promises to redefine the way developers conceive and execute their JavaScript applications.

Dec 06, 2023
what-are-the-emerging-trends-in-web-development image

What Are The Emerging Trends In Web Development?

Can you fathom the lightning speed at which the web development landscape is evolving? It feels like just yesterday we marveled at parallax scrolling, and today, we're taking a quantum leap into the captivating realm of 3D.

Nov 17, 2023

Contact Us

We have a good offer for you

clock icon

15 minutes of consultation

shield icon

Strict non-disclosure policy

window icon

Involvement of High-Level Developers to your Project

hand-shake icon

Fruitful Cooperation & Prominent Increment

Server error. Please, try in a few minutes again
Call Back