Creating custom code on back-end and front-end using extension points
Disclosed herein are system, method, and computer program product embodiments for providing extension points to alter a data source in a data pipeline. By providing a before-state-change extension point, a data orchestration system may allow connected clients to aggregate delta from a changed state source, allowing the data orchestration system to include only changed or added data in a transferred data state. By providing an after-state-change extension point, a data orchestration system may harness additional customizations, for example, effectively and efficiently handle changes to the state made by a viewing client following the transmission of a delta of changes.
1. A computer implemented method, comprising:
associating, by one or more processors, a before-state-change extension point comprising a first set of executable instructions with a data source in a data orchestration system, wherein the first set of executable instructions are received in a configuration tool provided by the data orchestration system;
sending, by the one or more processors, an initial state reflecting the data source to a front-end;
receiving, by the one or more processors, a modification to the initial state from a data repository based upon the data source and transformation steps performed on data;
determining, by the one or more processors, a changed state, wherein the changed state comprises a delta of changes representing the modification to the initial state based upon a change to the data source in light of changes in the data repository;
sending, by the one or more processors, the delta of changes and the first set of executable instructions to the front-end;
performing, by the one or more processors, one or more transformational operations on the transformed state in a data processing pipeline; and
causing, by the one or more processors, the front-end to execute the first set of executable instructions against the changed state after receiving the delta of changes to derive a transformed state and display the transformed state.
2. The method of claim 1 , further comprising:
associating, by the one or more processors, an after-state-change extension point comprising a second set of executable instructions with the data source; and
causing, by the one or more processors, the front-end to execute the second set of executable instructions after displaying the transformed state.
3. The method of claim 1 , further comprising:
determining, by the one or more processors, that the first set of executable instructions was configured; and
causing, by the one or more processors, the front-end to render the transformed state for view in a scene.
4. The method of claim 1 , further comprising:
determining, by the one or more processors, that the first set of executable instructions was not configured and
causing, by the one or more processors, the front-end to render the changed state for view in a scene.
5. The method of claim 1 , the receiving further comprising:
binding, by the one or more processors, the initial state to an HTML, element;
receiving, by the one or more processors, an interaction with an element in a scene displayed on the front-end; and
determining, by the one or more processors, the changed state based on the interaction.
6. The method of claim 1 , further comprising:
performing, by the one or more processors, a data-transforming operation on the data source as specified in a data processing pipeline designed in the configuration tool.
7. The method of claim 1 , further comprising:
causing, by the one or more processors, the front end to simultaneously display data from a second data source with the transformed state.
8. A system, comprising:
a memory; and
at least one processor coupled to the memory and configured to:
associate a before-state-change extension point comprising a first set of executable instructions with a data source in a data orchestration system, wherein the first set of executable instructions are received in a configuration tool provided by the data orchestration system;
send an initial state reflecting the data source to a front-end;
receive a modification to the initial state from a data repository based upon the data source and transformation steps performed on data;
determine a changed state, wherein the changed state comprises a delta of changes representing the modification to the initial state based upon a change to the data source in light of changes in the data repository;
send the delta of changes and the first set of executable instructions to the front-end;
perform one or more transformational operations on the transformed state in a data processing pipeline; and
cause the front-end to execute the first set of executable instructions against the changed state after receiving the delta of changes to derive a transformed state and display the transformed state.
9. The system of claim 8 , the at least one processor further configured to:
associate an after-state-change extension point comprising a second set of executable instructions with the data source; and
cause the front-end to execute the second set of executable instructions after displaying the transformed state.
10. The system of claim 8 , the at least one processor further configured to:
determine that the first set of executable instructions was configured; and
cause the front-end to render the transformed state for viewing in a scene.
11. The system of claim 8 , the at least one processor further configured to:
determine that the first set of executable instructions was not configured; and
cause the front-end to render the changed state for view in a scene.
12. The system of claim 8 , wherein to receive the changed state, the at least one processor is configured to:
bind the initial state to an HTML element;
receive an interaction with an element in a scene displayed on the front-end; and
determine the changed state based on the interaction.
13. The system of claim 8 , the at least one processor further configured to:
perform a data-transforming operation on the data source as specified in a data processing pipeline designed in the configuration tool.
14. The system of claim 8 , the at least one processor further configured to:
cause the front end to simultaneously display data from a second data source with the transformed state.
15. A non-transitory computer-readable device having instructions stored thereon that, when executed by at least one computing device, cause the at least one computing device to perform operations comprising:
associating a before-state-change extension point comprising a first set of executable instructions with a data source in a data orchestration system, wherein the first set of executable instructions are received in a configuration tool provided by the data orchestration system;
sending an initial state reflecting the data source to a front-end;
receiving a modification to the initial state from a data repository based upon the data source and transformation steps performed on data;
determining a changed state, wherein the changed state comprises a delta of changes representing the modification to the initial state based upon a change to the data source in light of changes in the data repository;
sending the delta of changes and the first set of executable instructions to the front-end;
performing one or more transformational operations on the transformed state in a data processing pipeline; and
causing the front-end to execute the first set of executable instructions against the changed state after receiving the delta of changes to derive a transformed data state and display the transformed state.
16. The non-transitory computer-readable device of claim 15 , the operations further comprising:
associating an after-state-change extension point comprising a second set of executable instructions with the data source; and
causing the front-end to execute the second set of executable instructions after displaying the transformed state.
17. The non-transitory computer-readable device of claim 15 , the operations further comprising:
determining that the first set of executable instructions was not configured;
causing the front-end to render the changed state for view in a scene.
18. The non-transitory computer-readable device of claim 15 , the operations further comprising:
binding the initial state to an HTML, element;
receiving an interaction with an element in a scene displayed on the front-end; and
determining the changed state based on the interaction.
19. The non-transitory computer-readable device of claim 15 , the operations further comprising:
performing a data-transforming operation on the data source as specified in a data processing pipeline designed in the configuration tool.
20. The non-transitory computer-readable device of claim 15 , the operations further comprising:
causing the front end to simultaneously display data from a second data source with the transformed state.