Distributed designs for web applications are in demand. However, without preventive measures, such programs are often more susceptible to DoS attacks. But why is it like that? The following example quickly shows this.
In a Denial of Service attack, a provider is flooded with a large number of requests until it ultimately fails due to overload. In addition to DoS attacks, attacks that are started simultaneously from many distributed devices and with the blocking of the source – can be blocked.
Typical web apps and e-commerce programs are mostly still monolithic. That means: A software stands behind all functionalities and thus delivers all pages and data to the user. If such a network is attacked and then fails as a result, it is no longer possible to work on the system. Concurrent processes such as ordering, payment or the editing of new content and products no longer work. Distributed designs each have their own software components for dedicated tasks, such as prices, availability, product presentation, customer self care, login and user management and order processing.
The Advantages Of Such Distributed Designs Are Obvious
If an attacker takes control of one component, he does not have access to the data of the others. If he overloads them, the functionality of the others is retained. In addition, the base of individual components is smaller and therefore easier to maintain independently of the remaining materials. In addition, the individual areas of the system can be scaled more precisely and in line with requirements. At first glance, it seems that distributed designs are much better suited to countering DoS attacks than typical ones.
In a monolithic app with only one database, all this data can be compiled with a persistent channel using around 25-30 queries. Often the database is also installed on the same server, so that no system communication is necessary.