Skip to content

Commit 256c898

Browse files
author
gitName
committed
wscon
1 parent c8d2e20 commit 256c898

File tree

6 files changed

+17
-7
lines changed

6 files changed

+17
-7
lines changed

articles/api-management/api-management-key-concepts.md

Lines changed: 6 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -100,15 +100,16 @@ Using the developer portal, API consumers can:
100100
* Download API definitions
101101
* Manage API keys
102102

103-
## API platform deployment models
103+
## Federated API platform deployment with workspaces
104104

105-
Azure API Management supports several deployment models for managing an organization's APIs, including *centralized*, *siloed*, and *federated*. The models offer different degrees of centralized control over the API platform infrastructure and autonomy of teams that produce and manage APIs.
105+
Azure API Management supports several deployment models for managing an organization's API portfolio, including *centralized*, *siloed*, and *federated*. The models offer different degrees of centralized control over the API platform infrastructure, API governance, and API discovery. For organizations that want to manage API complexity by empowering decentralized teams to develop and manage their own APIs, API Management supports a federated model with workspaces.
106106

107-
See the following table for a comparison of these models.
107+
[!INCLUDE [workspaces-benefits](../../includes/workspaces-benefits.md)]
108108

109-
[!INCLUDE [api-management-platform-deployment-models](../../includes/api-management-platform-deployment-models.md)]
109+
**More information**:
110110

111-
For example, a centralized model may be appropriate for smaller organizations that prioritize uniform API governance and cost-efficiency, while a federated model may be best for organizations that want to empower decentralized teams to develop and manage their own APIs using [workspaces](#workspaces).
111+
* [Workspaces in API Management](workspaces-overview.md)
112+
* [API Management deployment models](workspaces-overview.md#centralized-api-platform-and-decentralized-api-teams)
112113

113114
## API Management tiers
114115

articles/api-management/workspaces-overview.md

Lines changed: 1 addition & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -18,8 +18,7 @@ ms.author: danlep
1818

1919
Today, organizations increasingly face challenges in managing a proliferation of APIs. As the number of APIs and API development teams grows, so does the complexity of managing them. This complexity can lead to increased operational overhead, security risks, and reduced agility. On the one hand, organizations want to establish a centralized API infrastructure to ensure API governance, security, and compliance. On the other hand, they want their API teams to innovate and respond quickly to business needs, without the overhead of managing an API platform.
2020

21-
In API Management, *workspaces* bring a new level of autonomy to an organization's API teams, enabling them to create, manage, and publish APIs faster, more reliably, securely, and productively within an API Management service. By providing isolated administrative access and API runtime, workspaces empower API teams while allowing the API platform team to retain oversight. This includes central monitoring, enforcement of API policies and compliance, and publishing APIs for discovery through a unified developer portal.
22-
21+
[!INCLUDE [workspaces-benefits](../../includes/workspaces-benefits.md)]
2322
Workspaces function like "folders" within an API Management service:
2423

2524
* Each workspace contains APIs, products, subscriptions, named values, and related resources.

includes/workspaces-benefits.md

Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,10 @@
1+
---
2+
author: dlepow
3+
ms.service: azure-api-management
4+
ms.topic: include
5+
ms.date: 08/08/2023
6+
ms.author: danlep
7+
---
8+
9+
In API Management, *workspaces* bring a new level of autonomy to an organization's API teams, enabling them to create, manage, and publish APIs faster, more reliably, securely, and productively within an API Management service. By providing isolated administrative access and API runtime, workspaces empower API teams while allowing the API platform team to retain oversight. This includes central monitoring, enforcement of API policies and compliance, and publishing APIs for discovery through a unified developer portal.
10+

0 commit comments

Comments
 (0)