Session
The changing API problem
After a bad experience with some backend teams that changed the API without informing the frontend team in any way, we decided to introduce the API First paradigm in our development, adopting the OpenAPI specifications. This, together with a contract-based development, would allow us to detect such changes earlier and not reach critical moments at the end of the sprint.
One of the problems we encountered was than all the tools we found depend on java that allow, so we made the decision to build our own CLI in nodejs. From this need, several applications are born, aimed at different moments of development. Following the specifications contained in an OpenAPI file, we want to:
- automatically create code in javascript or typescript, both for client and server, so that we save a lot of time that we can spend thinking. This functionality is already available within the application openapi-nodejs-cli
- automatically create a mock server, which allows the front team not to have to wait for the API to be finished
- check that an API meets the indicated OpenAPI specifications, which allows us to test within the development flow for early detection of changes in the API
The session will tell the story behind the development and the use of the product. A small demo showing how it works and what you can do with it. Our talk is not fully technical, target audience is everyone involved in the software development cycle: Developers, Managers, Product Owners, Q.A .... It will take about 30m between talk and demo.

Julio César Abalde Reyes
Head at Corunet by Sngular
A Coruña, Spain
Links
Please note that Sessionize is not responsible for the accuracy or validity of the data provided by speakers. If you suspect this profile to be fake or spam, please let us know.
Jump to top