I see some services taking a requestId from the client as a mandatory attribute, while some services do not. I think it would be a good idea to have a request id from the clients, as this helps with debugging through logs, ie what happened to this request.
Can anyone give the good reasons or best practice API for the requestId?
Should the requestId be unique to the clients?
Is there any benefit in storing this ID in the database or for logging purposes only? At the moment I do not see any benefit in the database, but I wanted to ask anyway.