Enable javascript in your browser for better experience. Need to know to enable it? Go here.
radar blip
radar blip

Request-response events in user-facing workflows

Publicado : Nov 14, 2018
Not on the current edition
This blip is not on the current edition of the Radar. If it was on one of the last few editions it is likely that it is still relevant. If the blip is older it might no longer be relevant and our assessment might be different today. Unfortunately, we simply don't have the bandwidth to continuously review blips from previous editions of the Radar Understand more
Nov 2018
Resistir ? Continuar con precaución

On a number of occasions we have seen system designs that use request-response events in user-facing workflows. In these cases, the UI is blocked or the user has to wait for a new page to load until a corresponding response message to a request message is received. The main reasons cited for designs like this are performance or a unified approach to communication between backends for synchronous and asynchronous use cases. We feel that the increased complexity—in development, testing and operations—far outweighs the benefit of having a unified approach, and we strongly suggest to use synchronous HTTP requests when synchronous communication between backend services is needed. When implemented well, communication using HTTP rarely is a bottleneck in a distributed system.


Descarga el Radar Tecnológico Volumen 25


English | Español | Português | 中文


Mantente informada sobre Tecnología


Suscríbete ahora

Visita nuestro archivo para leer los volúmenes anteriores