You're viewing Apigee Edge documentation.
View Apigee X documentation.
On April 18, 2016, we released a new version of Apigee Edge Microgateway.
New features and enhancements
Following are the new features and enhancements in this release.
Single process server
Edge Microgateway is now a single process server. It no longer uses a two process model where one process (previously known as the "agent") launches Edge Microgateway, the second process. The new architecture makes automation and containerization easier.
Namespaced configuration files
Configuration files now are namespaced using organization and environment so that multiple Microgateway instances can run on the same host. You can find the config files in ~/.edgemicro after you run the Edge Microgateway config command.
New environment variables
There are now 4 environment variables: EDGEMICRO_ORG, EDGEMICRO_ENV, EDGEMICRO_KEY, EDGEMICRO_SECRET. If you set these variables on your system, you do not have to specify their values when you use the Command-Line Interface (CLI) to configure and start Edge Microgateway.
Edge Microgateway uses a cached configuration file if it restarts with no connection to Apigee Edge.
There are now options to start Edge Microgateway in cluster mode. Cluster mode allows you to take advantage The microgateway employs the Node.js cluster module for this feature. For details, see the Node.js documentation.
Plugin event lifecycle now properly handles async code that contains code with a new callback.