A command sequence processing method, comprising: a) receiving, by a server in a server cluster, a target request that carries a target command and that is sent by a client, wherein the target command is corresponding to a target context number, wherein a context number is a unique identifier of a context corresponding to the client and the context is obtained by combining multiple threads associated to a command execution sequence; b) using a current time as a target timestamp of the target request; c) adding a local associated command corresponding to the target context number and a local conflicted command in read/write conflict with the target command to a target dependency set; d) forwarding the target request to a replica server in the server cluster, updating the target dependency set according to a feedback from the replica server, and storing an updated target dependency set synchronously with the replica server, so that the replica server subsequently executes a command according to the updated target dependency set; and e) determining a target execution sequence of the target command and each command in the updated target dependency set according to the target context number and the target timestamp that are corresponding to the target command, and a context number and a timestamp that are corresponding to each command in the updated target dependency set, and executing the target command and each command in the updated target dependency set according to the target execution sequence; and wherein the using a current time as a target timestamp of the target request comprises: f) detecting whether the target request comprises a preset timestamp; and f1) if it is detected that the target request does not comprise the preset timestamp, using the current time as the target timestamp of the target request; and f2) if it is detected that the target request comprises the preset timestamp, adding the target request to a wait queue; and when it is detected that a time arrives at the preset timestamp, extracting the target request from the wait queue, and using the preset timestamp in the target request as the target timestamp of the target request; and wherein the adding a local associated command corresponding to the target context number and a local conflicted command corresponding to the target command to a target dependency set comprises: g1) locally detecting a first to-be-processed request that carries a context number equal to the target context number and a timestamp less than the target timestamp, using a command in the first to-be-processed request as the associated command, and adding the associated command to the target dependency set; and g2) locally detecting a second to-be-processed request that carries a context number unequal to the target context number and a command in read/write conflict with the target command, using the command in the second to-be-processed request as the conflicted command, and adding the conflicted command to the target dependency set. a) receiving, by a server in a server cluster, a target request that carries a target command and that is sent by a client, wherein the target command is corresponding to a target context number, wherein a context number is a unique identifier of a context corresponding to the client and the context is obtained by combining multiple threads associated to a command execution sequence; b) using a current time as a target timestamp of the target request; c) adding a local associated command corresponding to the target context number and a local conflicted command in read/write conflict with the target command to a target dependency set; d) forwarding the target request to a replica server in the server cluster, updating the target dependency set according to a feedback from the replica server, and storing an updated target dependency set synchronously with the replica server, so that the replica server subsequently executes a command according to the updated target dependency set; and e) determining a target execution sequence of the target command and each command in the updated target dependency set according to the target context number and the target timestamp that are corresponding to the target command, and a context number and a timestamp that are corresponding to each command in the updated target dependency set, and executing the target command and each command in the updated target dependency set according to the target execution sequence; and f1) if it is detected that the target request does not comprise the preset timestamp, using the current time as the target timestamp of the target request; and f2) if it is detected that the target request comprises the preset timestamp, adding the target request to a wait queue; and when it is detected that a time arrives at the preset timestamp, extracting the target request from the wait queue, and using the preset timestamp in the target request as the target timestamp of the target request; and g1) locally detecting a first to-be-processed request that carries a context number equal to the target context number and a timestamp less than the target timestamp, using a command in the first to-be-processed request as the associated command, and adding the associated command to the target dependency set; and g2) locally detecting a second to-be-processed request that carries a context number unequal to the target context number and a command in read/write conflict with the target command, using the command in the second to-be-processed request as the conflicted command, and adding the conflicted command to the target dependency set.