Composable processing framework based on web assembly component model
In an example embodiment, a common, composable abstraction is provided that allows components to work efficiently across programming languages and services without the need to write glue code. Application developers can concentrate on the application logic itself. The functionality of services can be developed by framework developers only once, using the programming language of their choice.
1. A system comprising:
at least one hardware processor; and
a computer-readable medium storing instructions that, when executed by the at least one hardware processor, cause the at least one hardware processor to perform operations comprising:
accessing a data model, the data model comprising a definition of entities and their relationships and definitions of services that operate on the entities;
compiling the data model into a component model;
compiling the component model into a user programming language, the user programming language being a programming language compilable into a bytecode format;
accessing custom code, written in the user programming language, the custom code including the compiled component model;
compiling the custom code into the bytecode format;
loading the compiled custom code into a framework running a host programming language; and
executing the compiled custom code to create a server process.
2. The system of claim 1 , wherein the server process further contains at least one interface, based on the component model, that translates input to the custom code from a first format into the host programming language, and at least one interface, based on the component model, that translates output from the custom code from the host programming language into the first format.
3. The system of claim 2 , wherein the first format is Hypertext Transfer Protocol (HTTP).
4. The system of claim 1 , wherein the bytecode format is WebAssembly.
5. The system of claim 4 , wherein the component model is a WebAssembly component model (WASM).
6. The system of claim 1 , wherein the host programming language is Core Query Notation.
7. The system of claim 1 , wherein the framework compiles the compiled component model into an interface compatible with the host programming language.
8. A method comprising:
accessing a data model, the data model comprising a definition of entities and their relationships and definitions of services that operate on the entities;
compiling the data model into a component model;
compiling the component model into a user programming language, the user programming language being a programming language compilable into a bytecode format;
accessing custom code, written in the user programming language, the custom code including the compiled component model;
compiling the custom code into the bytecode format;
loading the compiled custom code into a framework running a host programming language; and
executing the compiled custom code to create a server process.
9. The method of claim 8 , wherein the server process further contains at least one interface, based on the component model, that translates input to the custom code from a first format into the host programming language, and at least one interface, based on the component model, that translates output from the custom code from the host programming language into the first format.
10. The method of claim 9 , wherein the first format is Hypertext Transfer Protocol (HTTP).
11. The method of claim 8 , wherein the bytecode format is WebAssembly.
12. The method of claim 11 , wherein the component model is a WebAssembly component model (WASM).
13. The method of claim 8 , wherein the host programming language is Core Query Notation.
14. The method of claim 8 , wherein the framework compiles the compiled component model into an interface compatible with the host programming language.
15. A non-transitory machine-readable medium storing instructions which, when executed by one or more processors, cause the one or more processors to perform operations comprising:
accessing a data model, the data model comprising a definition of entities and their relationships and definitions of services that operate on the entities;
compiling the data model into a component model;
compiling the component model into a user programming language, the user programming language being a programming language compilable into a bytecode format;
accessing custom code, written in the user language, the custom code including the compiled component model;
compiling the custom code into the bytecode format;
loading the compiled custom code into a framework running a host programming language; and
executing the compiled custom code to create a server process.
16. The non-transitory machine-readable medium of claim 15 , wherein the server process further contains at least one interface, based on the component model, that translates input to the custom code from a first format into the host programming language, and at least one interface, based on the component model, that translates output from the custom code from the host programming language into the first format.
17. The non-transitory machine-readable medium of claim 16 , wherein the first format is Hypertext Transfer Protocol (HTTP).
18. The non-transitory machine-readable medium of claim 15 , wherein the bytecode format is WebAssembly.
19. The non-transitory machine-readable medium of claim 18 , wherein the component model is a WebAssembly component model (WASM).
20. The non-transitory machine-readable medium of claim 15 , wherein the host programming language is Core Query Notation.