Which tier is NOT part of the API-led connectivity architecture?

API-led connectivity consists of three primary tiers: Experience, Process, and System. Each plays a crucial role in enabling connectivity and streamlining integration within an organization.

The Experience tier focuses on how consumers interact with APIs, providing a way for end users to engage with the data and services efficiently. It ensures that the APIs are user-friendly and accessible, catering to various applications and devices.

The Process tier serves as the intermediary that orchestrates the business logic between various systems. It combines and transforms data by using APIs to enable seamless communication and workflows, ensuring that the right data is delivered to the right place at the right time.

The System tier, on the other hand, covers the legacy applications and databases where the data resides. This tier is responsible for making core system integrations accessible via APIs, ensuring that the underlying capabilities are exposed to more modern applications.

While the Infrastructure tier is essential for deploying and managing the underlying systems—such as servers, networks, and storage—it does not constitute a part of the API-led connectivity architecture's three foundational tiers. Therefore, identifying Infrastructure as not part of the architecture helps clarify the specific focus areas of API-led connectivity, which is primarily concerned with how APIs are structured and leveraged across different solutions and systems.