Compare APIM 3.0 with Classic APIM

APIM 3.0 builds on Classic APIM by adding capabilities required for modern, growing API programs. APIM 3.0:

• Delivers seamless data and application integration using Services as the building blocks for composability.

• Provides agility to structure domain- and data-driven Services as APIs efficiently and reliably.

• Reduces time-to-market for building and publishing Services.

• Augments API programs with capabilities that help growing businesses scale operations and adapt to changing needs.

• Enables standardization of governance with built-in supervision, controls, and checks—without duplicating configuration.

• Provides automation to migrate Classic APIM APIs and Proxies to APIM 3.0 Services.

The primary difference between Classic APIM and APIM 3.0 is not the API implementation model, but how APIs and governance are modeled, reused, and operated.

• Supports two API implementation approaches:

  • Proxies that front third-party or external endpoints.

  • Native SnapLogic APIs, implemented and executed within SnapLogic.

• APIs are managed individually, regardless of implementation type, and cannot be combined.

• Governance is supported, but is typically:

  • Defined per API or API version.

  • Copied and customized rather than reused.

• Configuration grows linearly with the number of APIs.

• User interface reflects earlier design patterns and workflows.

• Like Classic APIM, APIM 3.0 supports proxies and native SnapLogic APIs. However, they are modeled as Services designed for reuse and multiple endpoints can be combined in one Service.

• Governance is implemented through reusable Policies composed of individual rules.

• Common patterns are defined once and applied consistently.

• Designed explicitly for composability and domain-driven services.

• Includes a modernized user interface optimized for scale and usability.

Classic APIM and APIM 3.0 have a common foundation. The intentional continuity enables you to evolve API management without changing the underlying implementation models. Both Classic APIM and APIM 3.0 support:

• APIs implemented as proxies in front of third-party or external endpoints.

• Native SnapLogic task APIs that execute pipelines on the SnapLogic infrastructure.

• The same policy hierarchy:

• Governance controls such as authentication, authorization, rate limiting, and traffic management.

• A developer portal to publish APIs for consumption.

A key improvement of APIM 3.0 is the new interface. The image below shows the API Manager in Classic APIM on the left and the Service catalog in APIM 3.0 on the right.

Open

The following table maps the Classic APIM interface to APIM 3.0 interface components:

Open

For more information on APIM 3.0, refer to the following resources:

• Getting started with APIM 3.0

• Hello World Tutorial

• Move from Classic APIM to APIM 3.0

• Introduction to Services

• Introduction to Policies

• Manage the Developer Portal

• Use the Developer Portal