API driven architecture is not new, but most projects follow a more traditional route, where APIs are implemented first, before moving on in the DevOps cycle, where testing and integration happens at a later stage and this can create a lengthy feedback loop to the development team.
This can be improved if we treat APIs as “first-class citizens” and design them first. The API-first approach defines the API blueprint as the first step in the process where all parties review and agrees with a common API definition. From that point onwards, implementation, integration and testing can start in parallel, minimizing the lengthy, time consuming feedback loop to development team.
OpenAPI Specification (OAS) defines a standard, language-agnostic interface to RESTful APIs. With this specs and the plugins this framework provides it is the perfect way to implement and follow API-first architecture. In this session, you will learn the benefits of this approach and with practical examples and demos/live-coding you will see how easy it is to implement such architecture for your DevOps team.
6. • BA
• FO
Requirements
• Specs
• Mock
Design
• Specs
• Integration
Test
• UI
• Clients
Integration
• Code
• Deployment
Development
7. • The OpenAPI Specification (OAS) defines a
standard, language-agnostic interface to
RESTful APIs.
• Earlier (still) known as Swagger.
Open API Specification (OAS)
