Differences between Apigee Edge and Apigee X

Immutable when deployed

A similar but not identical solution is available. See Using AppGroups to organize app ownership.

Planned

• Asynchronous deployments
• Retrieving deployment status is based on the last time the runtime plane "checked-in" with the management plane

• Support for environment groups
• Self-service through the Apigee UI and APIs
• More flexibility in serving topology
• An MP pod can only serve one environment

For more information, see About environments and environment groups.

Please use Cloud Run or Cloud Functions

Planned

Use of [@.length-x] in JSONPath expressions is not supported in Apigee X. The JSONPath spec states that expressions are dependent on the underlying scripting language. length-x is a JavaScript construct, not Java, and [@.length-x] was not implemented as part of the spec. In Apigee X the expression [@.length-x] is superseded by the indexing scheme ([-x]).

For this example:

{
    "books": [
      {
        "name": "A",
      },
      {
        "name": "B",
      }
    ]
}

The input: $.books[@.length-1] returns {“name”: “B”} in Apigee Edge and returns [{“name”: “B”}] in Apigee X.

Northbound managed as Kubernetes secrets

• You can create encrypted, environment-scoped KVMs in the Apigee UI. KVMs are always encrypted. You cannot add, update, or view KVM entries in the UI.
• Use the private. attribute with all variables when accessing a KVM with the GET command to hide the KVM information in a debug (Trace) session. If the private. attribute is not used, the KVM is still encrypted; however, the KVM information will appear decrypted in the debug Trace) session and no exception will be thrown.
• You can manage KVM entries using the keyvaluemaps.entries API or the KeyValueMapOperations policy.
• You can use property sets for some of the same use cases as KVMs. See Using property sets.
• The <MapName> element enables the KeyValueMapOperations policy to identify which KVM to use dynamically, at runtime.

For more information on creating KVMs in the UI, see Using key value maps. See also Accessing configuration data for information on how to choose the right data persistence mechanism.

• Node.js API proxies are not supported.
• Apigee recommends that you host Node.js applications as separate containers in Kubernetes (same or different cluster)

• New policies:
  • AssertCondition policy: Evaluates a conditional statement at runtime in the request or response flows.
  • CORS policy: Allows JavaScript XMLHttpRequest (XHR) calls executed in a web page to interact with resources from non-origin domains.
  • DataCapture policy: Replaces the StatisticsCollector policy.
  • ExternalCallout policy: Sends gRPC requests to your gRPC server to implement custom behavior that isn't supported by Apigee policies.
  • GraphQL policy: Parses GraphQL payloads into message flow variables, verifies GraphQL requests against a schema, or both.
  • PublishMessages policy: Publishes your API proxy flow information to a Google Cloud Pub/Sub topic.
  • RevokeOAuthv2 policy: Revokes by user ID, app ID, or both.
  • TraceCapture policy: Adds additional variables to your Apigee runtime's trace data.
• Policy not supported:
  • StatisticsCollector policy (replaced by the new DataCapture policy)
• Changed policies:
  • MessageLogging policy: Does not support file logging

• Managed through Google Cloud console's IAM service
• Some curated out-of-the-box roles are available
• You can create custom roles which can include other Google Cloud permissions

For more information, see Users and roles.

For Apigee hybrid:

• The ingress is implemented through Anthos Service Mesh.
• The keys and certs are deployed directly to Kubernetes.

For Apigee X:

• Each instance exposes an HTTPS endpoint via self-signed certificate. The CA for the certificate can be downloaded by querying the org.