Where does a ScriptTarget node.js application run when deployed to Edge?

Apigee Edge executes Node.js applications within a specialized, open-source runtime environment called Trireme. Trireme is designed to run Node.js code directly on the Java Virtual Machine (JVM), which is the core of the Apigee Edge Message Processor. This architecture allows for tight integration between the Node.js application and the API proxy processing flow, enabling the script to interact with flow variables and other Apigee-specific features. Trireme provides the necessary compatibility layer to support many standard Node.js modules and asynchronous operations within the Apigee platform.

A. The Node.js application runs inside the Message Processor's JVM via Trireme, not in a separate, standalone Docker container.

B. While Apigee's Message Processor is Java-based, the specific runtime environment for executing Node.js code is Trireme, not Vert.x.

C. Trireme runs on the JVM and historically used a Java-based JavaScript engine (like Mozilla Rhino), not Google's native C++ V8 engine.

---

1. Google Cloud

Apigee Edge Documentation

"Adding Node.js to an API proxy": In the section "How does it work?"

the documentation states

"When you add a Node.js ScriptTarget to a proxy

Apigee creates a Node.js application that runs in a runtime environment called Trireme. Trireme is an open-source Node.js runtime that runs on the Java Virtual Machine (JVM)

which is part of Apigee Edge." This directly confirms that Trireme is the runtime environment.

2. Google Cloud

Apigee Edge Documentation

"Restrictions and limitations" (under Node.js): This section details the limitations imposed by the Trireme environment

such as restrictions on file system access and the use of native C++ modules

which are consequences of running Node.js on the JVM rather than a standard V8-based engine. This implicitly refutes the use of V8.

3. Trireme GitHub Repository (apigee/trireme): The official open-source repository for Trireme describes it as "a complete implementation of Node.js on the Java Virtual Machine." The project's README file provides architectural details that confirm it is a JVM-based runtime

distinct from standard Node.js.