api

API Design

login

Entry criteria

  1. The API uses architecture patterns promoting reusability for multiple API-consumers.
  2. The architecture ensures the APIs will integrate seamlessly with the infrastructure and platforms.
  3. Architecture requirements and decisions have been documented and validated with stakeholders.
  4. API is designed to meet API consumer needs hiding backend data models and discrepancies.
  5. The API and its endpoints have a description that explains its business value and features.
  6. API has a consistent design with our other API products.

logout

Exit criteria

  1. The API uses architecture patterns promoting reusability for multiple API-consumers.
  2. Architecture requirements and decisions have been documented and validated with stakeholders.
  3. API is designed to meet API consumer needs hiding backend data models and discrepancies.
  4. API interactions and data models have a consistent design with our other API products and design guidelines.

data_object

Doing the API work

Design API interactions based on identified requirements for API products. Document for API contract design and software delivery.
Helpful resources
settings

Enabling the API work

  •  Provide reusable templates, standards, and validation tools for API specifications

What type of API are you building?

API Cheat sheet helps you to understand the basic differences when building Private, Partner or Public APIs

Prototype

  1. No coding required.
  2. OpenAPI with examples
  3. Mock and test agains the prototype
  4. Give prototype out for comments and building for API consumers

Domain Canvas

What type of API are you building?

API Cheat sheet helps you to understand the basic differences when building Private, Partner or Public APIs


Build Just Enough

  1. Build so the interface works, it doesn't need to be super pretty, yet
  2. Protect with API management
  3. Set up CI/CD pipelines
  4. Do load testing, don't build for “theoretical future load”.

Scale

  1. Test coverage up, before optimizing
  2. Build for change
  3. Scale the API management
  4. Automate load testing.
  5. Check auto-scaling possibilities for all components but check also costs