---
# System prepended metadata

title: API Delivery and SDLC
tags: [API, ' SDLC']

---

---
title: API Delivery and SDLC 
tags: API, SDLC
description: View the slide with "Slide Mode".
---

# API Delivery and SDLC 

<!-- Put the link to this slide here so people can follow -->
slide: https://hackmd.io/@bmWut0QBTlOgsogAMaLcpw/rkHM4shKB

---

## Sources:
1) a series of blog posts on An API Journey: From Idea to Deployment the Agile Way-Part I - Red Hat Developer on RedHat blog: [part 1](https://developers.redhat.com/blog/2018/04/11/api-journey-idea-deployment-agile-part1/), [part 2](https://developers.redhat.com/blog/2018/04/19/api-journey-idea-deployment-agile-way-part2/), [part 3](https://developers.redhat.com/blog/2018/04/26/api-journey-idea-deployment-agile-way-part3/)

## API journey by RedHat: Overview
![](https://developers.redhat.com/blog/wp-content/uploads/2018/04/end-to-end-flow-1024x474.png)

1) API Ideation 
2) API Contract Design
3) Expectations and Request/Response Samples
4) API Mocks and Ready-to-Use Tests
5) Developing, Deploying, and Testing
6) Continuous Testing of the API Implementation
7) API Exposition to the Outer World
---

## API journey by RedHat: API Ideation
- helpful to have a sandbox to test what future APIs should look like. 
- a “local” approach: to use a local tool that is dedicated to simulation. A drawback: mostly targeting developers and their “local” nature make it hard to easily share and tests multiple designs in the mid- or long-term. 
- An example [Hoverfly](https://hoverfly.io/)
- a “team” approach: to use a shared platform with mocking, comminucationa and sharing capabilities. 
- An Example: [Microcks](http://microcks.github.io/)

---
## API journey by RedHat: API Contract Design
- The purpose of this phase is to create an API contract artifact covering the technical and syntactic definition of the future API. A contract provides a clear description of the API methods and custom resources manipulated.

