Design

The 10x Engine transforms log/trace events into well-defined, typed TenXObjects to efficiently report on, regulate and optimize in edge and cloud environments.

Optimization Model

The 10x Engine employs a JIT optimization model inspired by Chrome V8’s intelligent design principle. Rather than treating each log event or JavaScript object as a "bag of properties," both engines assumes only a finite number of object shapes will emerge and that these shapes will follow stereotypical usage patterns.

Log events, like JavaScript objects, are not declared ahead of time. The 10x Engine records a template for each line shape as lines arrive and assigns it, as V8 assigns a cached hidden class, to every TenXObject of that shape for optimized, structured access. Names come from the symbol library compiled ahead of time and the rules in the run configuration; nothing is learned from traffic.

To learn more see TenXObjects.

AOT Compiler

To dynamically create class and metadata information at run time, the 10x AOT Compile pipeline scans GitHub and container repos ahead-of-time to generate symbol library files, similar to package artifacts (e.g., npm, .jar, .NET assembly).

The 10x run pipeline utilizes symbol library files to assign a shared TenXTemplate (i.e., hidden class) to input log/trace events with the same structure, creating a cached optimized schema for each event type.

Operating on typed objects enables direct access to symbol and variable values at runtime without repeatedly parsing JSON structures or evaluating complex, brittle regular expressions for each event.