We have two separate systems communicating via a web service. Call them the interface and the interface. Most processing involves updating lists in the background. For example, the front interface needs to update a specific face. We are currently developing an interface where we decide what the interface should be. We will need the actual database identifiers to update the base database, but we also see that distributing database identifiers to our consumers may be a bad idea.
What alternatives force clients (e.g. front-end) to send identifiers back to the web service to update a specific object? Another reason we try to avoid identifiers is because the interface often saves these changes, which will be sent later. This will require the interfaces to store our identifiers in their system, which also seems bad.
We reviewed the following:
1) Send database identifiers to the fore; they would have to send them back to process the change
2) Send hashed identifiers (based on database identifiers) back to the front-end; they would have to send them back to process the changes.
3) Do not force clients to send identifiers at all, but they send the original entity and the new entity and "match" our entity in the database. Their original essence must correspond to our stored object. We must also determine what constitutes a match between our organization and its new entity.
source
share