Channel
Interviewed Person
Javi Velasco
[Music] [Applause] thank you okay hello everyone it's great to be back in a presidential event after all of this struggle all this time so i'm very grateful to be here with you today um i mean the introduction was already pretty good so i want to still give you a bit of context on myself um my name is javi and that is my twitter handle and my dog as usual
and um a few years ago like 90 of my work was basically front-end stuff right um which is surprising if you consider the talk that i'm about to do and i wrote this material ui kit called react toolbox and i'm sorry if you ever used it because i abandoned the project and and i joined brazil quite a few years ago when it was still called
side and yeah and since then i spent a lot of time working on apis and tooling in general and or internal developer experience so in case you're not familiar with what burcell is it is the fastest way to deploy front-end applications so we enable collaboration by giving front-end developers comprehensive tools to build high-performance websites and our mission is to build a better web faster with personal you can connect
a repository from any git provider and you would instantly generate multi-cloud deployments that are globally available through our edge network with every git push but if you're done it doesn't ring a bell for you you might never sell for being the company behind the super popular framework next yeah yes all right that's with introductions so what is this talk about from the title is gonna sound like it's a very very very technical talk it is
not that technical it's more about sharing a story like sharing the story or for api um it also starts a few years back when we had a lot of microservices in a crazy distributed system that was very difficult to deal with and building new stuff for the system was really painful you're going to see why so we ended up building a framework and then adding some extra tooling on that framework and then the ultimate goal was
to generate an open api spec for our api which is why the talk is called like that so what is the open api specification everybody that is anybody familiar with it already i'm not sure about the background of you guys okay yeah kind of right so the open api specification is an industry standard for describing modern apis right
and it's the most probably adopted is to industry standard to describe apis in a machine readable form language so it basically allows you to describe your api available endpoints and operations parameters for each operation authentication methods and metadata like contact data authors and and yeah license and so on so why should we use that and especially
why should we use it adversely the most important reason to use this is that it enables static analysis so you have a formal representation for api right and you can pretty much build tools on top of it in order to do interesting stuff like for example comparing a previous version of your api with a new version and there's tooling already that would tell you if you are rolling a breaking change or if there is an
