ArchitectureA supervised JVM-class runtime — OLTP on seven engines, OLAP on three. AI-native, MCP-native, observable as plain SQL.Read the architecture
Está viendo la edición Perú. Está viendo la edición Colombia. You're viewing the Pakistan edition. Cambiar a la edición global →Cambiar a la edición global →Switch to the global edition →

Every server switch declared once, with its default and meaning, at startup

Every -D system property a node obeys is now declared once with its name, default and meaning, read through that declaration, listed in the startup box, and flagged when set away from its default.

JVM system properties are the quiet configuration of a Java server: easy to add in code, hard to discover from outside, and easy to leave set long after anyone remembers why. This release makes them a declared, checked list.

Declared once

  • Name, default, meaning Each switch the core and the Studio node read is declared in one place, with a one-line description, and code reads it through that declaration.
  • One naming scheme Ten core switches were renamed to axional.<area>.<setting>, with the unit last where there is one; the old names were removed rather than aliased.
  • Held by tests A test scans the source and fails on a property read but not declared, or read by its literal name; another fails on any retired name left in code, build files or documentation.

Visible at startup

  • The startup box Lists every switch of the node; one set away from its default is shown as a warning with its value.
  • Retired names The startup box also names the switches that were retired, so an old launch script is caught on the first boot.

A node now says, as it starts, every setting it runs with that differs from the product's defaults.