You're viewingApigee Edge documentation.
Go to theApigee X documentation.info

Private Cloud Deprecation Notice:

Support forNode.js proxies andsecure vaults

Since 2013, Apigee has supported theuse of Node.js proxies within Apigee Edge through the use ofTrireme, which enables you to run your Node.js code within Apigee Edge for Private Cloud and expose it as an API.

Apigee recommends Private Cloud customers take the following steps:

• Migrate data in secure vaults toEncrypted Key Value Maps (KVM) to access sensitive data from an API proxy.
• Migrate Trireme (Node.js) based API proxies to a native Node.js environment outside of Apigee.

See alsoApigee deprecations and retirements.

Public Cloud Retired feature: The traditional, Trireme-based Node.js support on Apigee Edge Cloud is retired and, by extension,apigee-access is also retired because it is only used in Trireme-based Node.js applications deployed on Apigee Edge. Trireme-based Node.js was retired on October 10, 2019. SeeTrireme-based Node.js End of Life.

The traditional Node.js support on Apigee Edge provides an embedded Node.js runtime environment that is scoped to an Apigee organization and environment. Node.js applications deployed to this environment can serve as the target for any API proxies that are deployed to that same organization/environment.

The traditional Edge Node.js support relies internally on an open-source bridge application called (Trireme) and a JavaScript interpreter called (Rhino) that allow Node.js code to execute in the Edge Java runtime environment.

There are several limitations associated with this approach. For example:

• Only an older version of Node.js (0.10.32) is supported.
• There are subtle differences in behavior between the standard Node.js environment and the Trireme/Rhino environment.
• Debugging Node.js apps after they are deployed to Edge is difficult.

Node.js apps deployed to Hosted Targets do not depend on any Apigee-specific Node.js run-time technology. Your Node.js app will run in Hosted Targets exactly as it runs in your local development environment.

Samples

Sample:You can download Node.js from thesamples repository on GitHub. proxy sample code. See alsoUsing the sample API proxies.

The Node.js repository contains a number of basic examples from deploying a simple Hello World! server to an employee database API that leverages a cloud-based datastore.

Performance tips

SeeNode.js Performance Tips: Socket Pooling in the Apigee Community.

Next Steps

Now that you know a little about Node.js support in Apigee Edge, it's time to see Node.js on Edge in action. In the next topic,Getting started with Node.js on Apigee Edge, we'll show you how to proxy a very simple "Hello World" Node.js app on Apigee Edge using the management UI. Later, we'll show you how to deploy Node.js apps directly from your development machine to Edge using the command-line interface.

Limitations

Traditional EdgeNode.js support relies internally on an open-source bridge application (Trireme) and a JavaScript interpreter (Rhino) that allow Node.js code to execute in the Edge Java runtime environment.

There are several limitations associated with this approach. For example:

• Only an older version of Node.js (0.10.32) is supported.
• There are subtle differences in behavior between the standard Node.js environment and the Trireme/Rhino environment.
• Debugging Node.js apps after they are deployed to Edge is difficult.