A method for performing an idempotent service operation, the method comprising: generating, by a service request side, a service processing request for a service event, wherein the service processing request comprises service processing reference information; sending, by the service request side, the first service processing request to the service processing side; in response to receiving the service processing request, determining, by the service processing side and based on the service processing reference information included in the service processing request, a corresponding storage location of service-related data in a database, wherein the corresponding storage location comprises one of multiple different storage locations that each separately maintain a respective idempotent table; performing, by the service processing side, an idempotent check on the determined storage location, the performing comprising inserting unique identification information of the service processing request into an idempotent table maintained by the corresponding storage location; and either a) processing, by the service processing side, the service processing request based on a result of the idempotent check, the processing comprising, in response to successfully inserting the identification information in the idempotent table maintained by the corresponding storage location, processing the service processing request, or b) in response to failing to insert the identification information in the idempotent table maintained by the corresponding storage location, determining the service processing request to be a repeated request and stopping processing, by the service processing side, the service processing request; wherein the service processing reference information is used by the service processing side to determine a storage location of data associated with the service in a database, and service processing requests sent repeatedly for the same service event comprise the same service processing reference information. generating, by a service request side, a service processing request for a service event, wherein the service processing request comprises service processing reference information; sending, by the service request side, the first service processing request to the service processing side; in response to receiving the service processing request, determining, by the service processing side and based on the service processing reference information included in the service processing request, a corresponding storage location of service-related data in a database, wherein the corresponding storage location comprises one of multiple different storage locations that each separately maintain a respective idempotent table; performing, by the service processing side, an idempotent check on the determined storage location, the performing comprising inserting unique identification information of the service processing request into an idempotent table maintained by the corresponding storage location; and either a) processing, by the service processing side, the service processing request based on a result of the idempotent check, the processing comprising, in response to successfully inserting the identification information in the idempotent table maintained by the corresponding storage location, processing the service processing request, or b) in response to failing to insert the identification information in the idempotent table maintained by the corresponding storage location, determining the service processing request to be a repeated request and stopping processing, by the service processing side, the service processing request; a) processing, by the service processing side, the service processing request based on a result of the idempotent check, the processing comprising, in response to successfully inserting the identification information in the idempotent table maintained by the corresponding storage location, processing the service processing request, or b) in response to failing to insert the identification information in the idempotent table maintained by the corresponding storage location, determining the service processing request to be a repeated request and stopping processing, by the service processing side, the service processing request; wherein the service processing reference information is used by the service processing side to determine a storage location of data associated with the service in a database, and service processing requests sent repeatedly for the same service event comprise the same service processing reference information.