Locations of Data and Systems

The Locations of Data and Systems Canvas maps where data resides and where API producers and consumers operate. This ensures the API platform architecture supports regulatory compliance, data sovereignty, and efficient network interactions.

Detailed guide related to APIOps Cycles phase:
API Platform Architecture

How to Use:

  1. Map Data Locations:
    • Identify where your data (both master and copies) resides within the following scopes:
      • Company Network: Internal systems and storage.
      • Partner Network: Systems managed by third-party providers or collaborators.
      • Country Network: Data localized for specific geographies.
      • Global Network: Cloud or international data systems.
  2. Map API Producers and Consumers:
    • For each network scope, list the API producers and API consumers:
      • Producers: Teams or systems providing the API.
      • Consumers: Teams, applications, or partners consuming the API.
  3. Analyze Regulatory and Network Constraints:
    • Assess compliance requirements, such as GDPR or country-specific data localization laws.
    • Identify network limitations or inefficiencies that could affect API delivery.

Output:
A comprehensive view of data and system locations, regulatory considerations, and consumer-producer interactions to guide platform architecture decisions.

Back to related APIOps Cycles phase:
API Platform Architecture
APIOps Cycles

method for lean api development

Great APIs need skilled people and a good method, which let's you create APIs as products - fast.
APIOps Cycles method is vendor & technology-neutral.

Read the free e-book "The 8 wastes of lean in API development". Learn quick tips on how to remove the wastes using the APIOps Cycles method.