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.

Because neither JavaScript objects nor log events are defined or compiled ahead of time, both V8 and the 10x Engine infer structure dynamically at runtime by "listening" for patterns, gradually recognizing shared object shapes. Once identified, V8/10x assign cached hidden classes to TenXObjects to enable optimized, structured access.

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.