Event sourcing
In general, this disclosure involves systems, software, and computer implemented methods including receiving a mutate command instructing the modification of an object from a first state to a second state and accessing an event log including an origin state of the object, and one or more previously executed mutation commands. The one or more previously executed mutation commands are applied to the origin state of the object to determine whether the first state is valid. In response to determining that the first state is valid, executing the mutate command on the object to place the object in the second state and recording the mutate command in the event log as an additional, previously executed, mutation command.
1 . A method comprising:
receiving a mutate command instructing the modification of an object from a first state to a second state, wherein the object is a digital document comprising policy data, and wherein the modification of the first state to the second state comprises a change to the policy data;
accessing an event log comprising an origin state of the object, wherein the origin state is the state in which the object was instantiated, and one or more previously executed mutation commands;
applying the one or more previously executed mutation commands to the origin state of the object to generate a current state object;
comparing the current state object to the first state, and if the current state object matches the first state, determining that the first state is valid;
in response to determining that the first state is valid:
executing the mutate command on the object to place the object in the second state; and
recording the mutate command in the event log as an additional previously executed mutation command.
2 . The method of claim 1 , wherein the object is a component of a digital life insurance policy.
3 . The method of claim 1 , wherein the mutate command comprises changes to information in the object.
4 . The method of claim 1 , wherein if the current state object does not match the first state:
determining that the first state is invalid; and
returning a failure message indicating the object will not be placed in the second state.
5 . The method of claim 1 , wherein the one or more previously executed mutation commands each mutate the object from a previous state to a next state in a plurality of sequential states, and wherein the previously executed mutation commands are sequentially ordered.
6 . The method of claim 5 , comprising:
receiving a debug command request the object in a particular state of the plurality of sequential states;
accessing the event log and determining a subset of previously executed mutation commands that are sequentially ordered before the particular state; and
applying the subset of previously executed mutation commands, starting with an initially executed mutation command, to a debug object that is in the origin state to produce a debug object in the particular state of the plurality of sequential states.
7 . The method of claim 1 , comprising:
receiving a request for the object in a particular format;
accessing the event log;
applying the one or more previously executed mutation commands to the origin state of the object to create a current object;
converting the current object into the requested particular format; and
returning the object in the particular format.
8 . A non-transitory computer-readable storage medium storing one or more instructions executable by a computer system to perform operations comprising:
receiving a mutate command instructing the modification of an object from a first state to a second state, wherein the object is a digital document comprising policy data, and wherein the modification of the first state to the second state comprises a change to the policy data;
accessing an event log comprising an origin state of the object, wherein the origin state is the state in which the object was instantiated, and one or more previously executed mutation commands;
applying the one or more previously executed mutation commands to the origin state of the object to generate a current state object;
comparing the current state object to the first state, and if the current state object matches the first state, determining that the first state is valid;
in response to determining that the first state is valid:
executing the mutate command on the object to place the object in the second state; and
recording the mutate command in the event log as an additional previously executed mutation command.
9 . The computer-readable medium of claim 8 , wherein the object is a component of a digital life insurance policy.
10 . The computer-readable medium of claim 8 , wherein the mutate command comprises changes to information in the object.
11 . The computer-readable medium of claim 8 , wherein if the current state object does not match the first state:
determining that the first state is invalid; and
returning a failure message indicating the object will not be placed in the second state.
12 . The computer-readable medium of claim 8 , wherein the one or more previously executed mutation commands each mutate the object from a previous state to a next state in a plurality of sequential states, and wherein the previously executed mutation commands are sequentially ordered.
13 . The computer-readable medium of claim 12 , comprising:
receiving a debug command request the object in a particular state of the plurality of sequential states;
accessing the event log and determining a subset of previously executed mutation commands that are sequentially ordered before the particular state; and
applying the subset of previously executed mutation commands, starting with an initially executed mutation command, to a debug object that is in the origin state to produce a debug object in the particular state of the plurality of sequential states.
14 . The computer-readable medium of claim 8 , comprising:
receiving a request for the object in a particular format;
accessing the event log;
applying the one or more previously executed mutation commands to the origin state of the object to create a current object;
converting the current object into the requested particular format; and
returning the object in the particular format.
15 . A computer-implemented system, comprising:
one or more computers; and
one or more computer memory devices interoperably coupled with the one or more computers and having tangible, non-transitory, machine-readable media storing one or more instructions that, when executed by the one or more computers, perform one or more operations comprising:
receiving a mutate command instructing the modification of an object from a first state to a second state, wherein the object is a digital document comprising policy data, and wherein the modification of the first state to the second state comprises a change to the policy data;
accessing an event log comprising an origin state of the object, wherein the origin state is the state in which the object was instantiated, and one or more previously executed mutation commands;
applying the one or more previously executed mutation commands to the origin state of the object to generate a current state object;
comparing the current state object to the first state, and if the current state object matches the first state, determining that the first state is valid;
in response to determining that the first state is valid:
executing the mutate command on the object to place the object in the second state; and
recording the mutate command in the event log as an additional previously executed mutation command.
16 . The system of claim 15 , wherein the object is a component of a digital life insurance policy.
17 . The system of claim 15 , wherein the mutate command comprises changes to information in the object.