This part will take into account what we have to compute the placement. Let’s study the case of an HTTP request from a shopper to a system. The system as an entire, whatever the particular element, must compute the placement to know the place to save lots of the info.
Two instances can come up: the HTTP request might carry sufficient data to compute the place to ship the info to or not. Within the former case, it could be due to a shopper cookie, the earlier request set related information in hidden fields on an internet web page, or another method. Within the latter case, the system wants further information.
If the info is self-sufficient, it’s higher to ahead the request to the right nation as early within the request processing chain as attainable, i.e., from the API Gateway. Conversely, if the info requires enrichment, it needs to be carried out as near the info enrichment element as attainable.
Think about a scenario the place information location relies on a consumer’s residing place. We may set a cookie to retailer this data or information that enables us to compute it client-side. Each request would carry the info, and we wouldn’t want further information to compute the placement. Nevertheless, storing delicate information on the shopper is a danger, as malicious actors may tamper with storage.
To enhance safety, we may hold all the things server-side. The system would want to request further information to compute the placement on each request.
