Web application server and `Stack Vs Chain` problem
Implementation about a system to understand Stack Vs Chain and got some info to chain in case of problems
There is a big difference between the layer loading stack (the static one, from the platform core) and the actual execution stack (the one from the app runtime).
This main difference occurs due to the dynamic nature of server apps, which, if different from Express and closer to KOA or pure JavaScript, can call and concatenate in unexpected ways.
For example, kindness must wait for the subsequent layers to complete in order to obtain the final status of the response... but “which layers?”
This process must be defined differently from the common stack (a synchronous monolithic pancake). Its appropriate name is more “chain,” as a concatenation due to functionality and not position.
Adequate tools are needed to understand, monitor, and debug these flows.