WEBVTT 00:00.000 --> 00:14.000 Yeah, just one thing, first of all, my apologies, because yesterday we was drinking a lot. 00:14.000 --> 00:24.000 We were drinking out at the Lidium, I think I don't remember, but here we are, and we are going 00:24.000 --> 00:32.000 to present the IBA scoring. I don't know how many of you have ever worked with the IBA scoring. 00:32.000 --> 00:46.000 Hands up please, only one. Thanks, Renca. I love you. Well, so first, we are going to present the IBA scoring, 00:46.000 --> 00:54.000 well, with my colleague Alex, we are going to show how we apply the IBA scoring in our company, 00:54.000 --> 01:02.000 right? I have to share the, I don't make it. Okay, Rafa, but we have to be sure what kinds of things 01:02.000 --> 01:10.000 are we doing, because a great power becomes a great responsibility. 01:16.000 --> 01:20.000 Well, just one thing, how many of you are knowing the text? 01:20.000 --> 01:28.000 Okay, I'm sure I'm pretty sure that one of our brands could be known by you. 01:28.000 --> 01:34.000 But as you can see, we are not a company of our company, right? 01:34.000 --> 01:40.000 So the idea is that we have an engineering team, and we are working on open source tooling 01:40.000 --> 01:48.000 to share with yours, to talk about IBA scoring, and now we are going to present you. 01:48.000 --> 01:58.000 Okay, behind all of these brands and experience there is a great technology teams that make things happen like this. 02:18.000 --> 02:30.000 You know, you know, is this copyright in use or not? No, you can share. 02:30.000 --> 02:38.000 Okay, my, we have to do it that way, they pay our, or our flight team. 02:38.000 --> 02:46.000 So this is some numbers about the company. We have eight brands as you can see. 02:46.000 --> 02:54.000 We are in more than 200 markets, and also we have more than 5,000 stores around the world. 02:54.000 --> 03:02.000 So in the tech area, keeping in mind that we are working more than 1,000 people working on tech. 03:02.000 --> 03:14.000 We are making around 3,000 employees per year, and we have more than 6,000 repositories right now. 03:14.000 --> 03:20.000 So go ahead, Alex. 03:20.000 --> 03:28.000 Okay, if all of us, all of us are to they here, it is because they are being marketplaces still growing. 03:28.000 --> 03:36.000 The main reason not is of technology says that from now until 2013, the demand of the digital services is still growing. 03:36.000 --> 03:42.000 And which also means that the APIs, it will do the same. 03:42.000 --> 03:52.000 For example, market growth, the drivers, manufacturers like IT and telcos, challenge, geographical focus, 03:52.000 --> 04:02.000 and you know, they shall potentials like I increase customer experience or digital service creation. 04:02.000 --> 04:06.000 Okay, so let's go in deep. 04:06.000 --> 04:10.000 Without API, what happens? Nobody works, right? 04:10.000 --> 04:14.000 But again, I don't know. 04:14.000 --> 04:26.000 But if we have a lot of APIs in our repository, we have many, many brands in them. 04:26.000 --> 04:30.000 So what can we do to solve this solution? 04:30.000 --> 04:32.000 This is kind of things. 04:32.000 --> 04:36.000 The idea is to work with the quality of the API. 04:36.000 --> 04:38.000 What can we do? 04:38.000 --> 04:43.000 We have to work to solve some issues like technical debt, security risk, 04:43.000 --> 04:46.000 ecosystem fragmentation, scalability. 04:46.000 --> 04:52.000 And one that is for me, it's the word is the computational damage. 04:52.000 --> 04:56.000 If you make the things not quite well, 04:56.000 --> 05:00.000 the reputation damage could be very hard. 05:06.000 --> 05:11.000 Well, we are using linters, spectral and whatever. 05:11.000 --> 05:14.000 All of you are using linters, right? 05:14.000 --> 05:23.000 But linters are not enough for us to work with the quality of the APIs. 05:23.000 --> 05:28.000 We need to go in deep and we need to be excellent in our work. 05:28.000 --> 05:33.000 And we are using some other kind of tools to do that. 05:37.000 --> 05:42.000 Okay, after a deep search for the best tools that could fit for us. 05:42.000 --> 05:44.000 The three is here. 05:44.000 --> 05:46.000 Up inside by trouble, right? 05:46.000 --> 05:49.000 Read my API by suplo. 05:49.000 --> 05:58.000 And finally, all around tool open source by in the text take up is scoring. 05:58.000 --> 06:05.000 Okay, the first read my API, Rafa Delas. 06:05.000 --> 06:13.000 Okay, there are three tools to work with to know what is happening with our APIs. 06:14.000 --> 06:18.000 Each one has their own missiles, they have their own metrics. 06:18.000 --> 06:22.000 And they know there are some points that each one works with. 06:22.000 --> 06:29.000 So the idea is go one by one, step step and we will see a little demo of each one. 06:29.000 --> 06:34.000 Don't forget that the best of all is the last one is over API scoring. 06:36.000 --> 06:39.000 Again, here is one of the of them. 06:39.000 --> 06:43.000 You have a great my open API as it's an open source. 06:43.000 --> 06:46.000 You can upload your jammel. 06:46.000 --> 06:49.000 After that, you can use. 06:49.000 --> 06:50.000 Come on. 06:50.000 --> 06:53.000 You have to put to an email. 06:53.000 --> 06:57.000 And you have to put an email. 06:57.000 --> 07:00.000 But really, we need to put an email. 07:00.000 --> 07:02.000 We also have CLI. 07:02.000 --> 07:04.000 We also have a GitHub action. 07:04.000 --> 07:06.000 And of course, they have an API. 07:06.000 --> 07:14.000 So here, we can see a quick view of the specification and all the documentation that we have. 07:14.000 --> 07:20.000 But now, we are going to work with one of these tools. 07:20.000 --> 07:24.000 It's, we are going to see how it works. 07:24.000 --> 07:27.000 Yes, one moment. 07:27.000 --> 07:34.000 And now, I hope any of you knows these tools. 07:34.000 --> 07:37.000 OK. 07:37.000 --> 07:41.000 So here, we are going to work with a GitHub action. 07:41.000 --> 07:45.000 We have this jammel specification. 07:45.000 --> 07:47.000 This GitHub action. 07:47.000 --> 07:56.000 Now, we are going to work for each file with a jammel in the API index folder. 07:56.000 --> 07:59.000 And we have a couple of them. 07:59.000 --> 08:02.000 Here, we are going to use the Petestor. 08:02.000 --> 08:07.000 It's the typical one that is, I'm sure that all of you knows. 08:07.000 --> 08:12.000 And now, we are changing something in the code. 08:12.000 --> 08:18.000 Yes, to execute to launch the GitHub action. 08:18.000 --> 08:20.000 Here you have. 08:20.000 --> 08:24.000 We are going to change the more one with the more API days. 08:24.000 --> 08:27.000 It was the API days. 08:27.000 --> 08:33.000 And now, the GitHub action will be launched. 08:33.000 --> 08:41.000 And we will be, we will be able to see the results, the final results, and the scoring of the API. 08:41.000 --> 08:45.000 So here you have. 08:45.000 --> 08:48.000 Come on. 08:48.000 --> 08:51.000 Go to the action. 08:51.000 --> 08:53.000 As you can see, there are two jammel files. 08:53.000 --> 09:00.000 One of them is that the Petestor. 09:00.000 --> 09:02.000 Here, we have the results. 09:02.000 --> 09:09.000 But here, you can see some of the, of the ones that the tool, as, as talking through. 09:09.000 --> 09:14.000 One has to say in us that is something correct. 09:14.000 --> 09:19.000 Well, and here, you have the final results, it's 72. 09:19.000 --> 09:26.000 But you can see the final score with each one of the models that he is working. 09:26.000 --> 09:30.000 I mean, security is the key. 09:30.000 --> 09:37.000 Also, we have EA suggestions in order to change this. 09:37.000 --> 09:39.000 What is happening? 09:39.000 --> 09:42.000 And hey, maybe you have to define your security scheme here. 09:42.000 --> 09:44.000 So, well, let's go. 09:44.000 --> 09:45.000 Let's zone. 09:45.000 --> 09:46.000 And that's it. 09:46.000 --> 09:47.000 That's it. 09:47.000 --> 09:48.000 The first one. 09:48.000 --> 09:51.000 Read my open API. 09:51.000 --> 09:52.000 Okay. 09:52.000 --> 09:53.000 Next. 09:53.000 --> 09:55.000 I like this tool a lot. 09:55.000 --> 09:58.000 But we have more options. 09:58.000 --> 09:59.000 Right. 09:59.000 --> 10:01.000 The next is up inside. 10:01.000 --> 10:04.000 And come on. 10:07.000 --> 10:11.000 Well, we have another kind of tool. 10:12.000 --> 10:19.000 The great thing of this tool is, is that EA ready. 10:19.000 --> 10:25.000 Because when you go to the school and you go to the API account and academy, along the wall, 10:25.000 --> 10:31.000 all the people say, what is the client of the APIs? 10:31.000 --> 10:38.000 From now, the big client it's APIs has been done for developers by developers, right? 10:38.000 --> 10:41.000 But now, we have the EA. 10:41.000 --> 10:44.000 And the EA has to consume this API. 10:44.000 --> 10:47.000 So, this tool work on that. 10:47.000 --> 10:52.000 And we go ahead and we will see how it works. 10:52.000 --> 10:56.000 Here, we have the tools that they have. 10:56.000 --> 10:58.000 We have the CLA. 10:58.000 --> 11:01.000 We also have, I don't know why. 11:01.000 --> 11:05.000 But there are one application for IOS. 11:05.000 --> 11:06.000 I don't know. 11:06.000 --> 11:11.000 I don't want to give my API in my iPhone. 11:11.000 --> 11:14.000 But anyway, I don't understand. 11:14.000 --> 11:17.000 But it's here, right? 11:17.000 --> 11:19.000 You can do a lot if you want. 11:19.000 --> 11:24.000 But again, this is much more easy to use. 11:24.000 --> 11:32.000 But we have to keep in mind that we have the server running, because one of the keys of the analytics is 11:32.000 --> 11:35.000 to server inside about the performance. 11:35.000 --> 11:40.000 So you have to get the server running. 11:40.000 --> 11:44.000 Here, you have, again, we are going to use Petestor. 11:44.000 --> 11:49.000 After that, we get the inside. 11:49.000 --> 11:52.000 Here, we have the final score. 11:52.000 --> 11:53.000 61. 11:53.000 --> 11:56.000 Remember, we have 72 in the previous one. 11:56.000 --> 12:01.000 So here, we have the things that we have to change. 12:01.000 --> 12:08.000 Also, you can use in a pipeline or whatever. 12:08.000 --> 12:11.000 But this is the point. 12:11.000 --> 12:18.000 What I like is from this point, from this tool is because I like a lot the EA model. 12:18.000 --> 12:28.000 If we want to know if our API could be used in any way for the EA, maybe we have to use that. 12:28.000 --> 12:33.000 And finally, Alex? 12:33.000 --> 12:35.000 This is the best. 12:35.000 --> 12:41.000 I like it that I will include in my future APIs evaluating. 12:41.000 --> 12:46.000 But finally, app is coding is another tool by the text deck. 12:46.000 --> 12:51.000 And we are allowed to add up our nets. 12:51.000 --> 12:54.000 Rafa, that's nice. 12:54.000 --> 13:01.000 Well, when we start to work with the scoring, we need not only a tool, 13:01.000 --> 13:07.000 a typical tool to measure the scoring of the over API, 13:07.000 --> 13:11.000 because we also have our way paper to, you know, our internal company. 13:11.000 --> 13:18.000 And we also have our own rule set regarding the way paper, right? 13:18.000 --> 13:23.000 So what is API is coding in a text. 13:23.000 --> 13:24.000 API is coding. 13:24.000 --> 13:27.000 It's a set of tools assigned by us. 13:27.000 --> 13:29.000 We have our microservice. 13:29.000 --> 13:31.000 We also have our rules set. 13:31.000 --> 13:34.000 We also have the API folder to do the things. 13:34.000 --> 13:39.000 And, of course, to use in our pipelines. 13:39.000 --> 13:43.000 And we also have an idea extension for business studio. 13:43.000 --> 13:49.000 And we will take a look right now. 13:49.000 --> 13:52.000 Okay, here is the same, the potato store. 13:52.000 --> 13:55.000 And here we can see how it works. 13:55.000 --> 13:59.000 Don't forget that we are in the same phase. 13:59.000 --> 14:06.000 We think that to be honest, if we are building or writing one code, 14:06.000 --> 14:10.000 and we have to wait until the end to know what is happening, 14:10.000 --> 14:15.000 maybe it's a sheet, can I say this one here? 14:15.000 --> 14:20.000 So the idea is to know what is happening in this phase. 14:20.000 --> 14:24.000 So right now, if we are building this code, 14:24.000 --> 14:29.000 we know that we have some mistake in the security phase. 14:29.000 --> 14:37.000 Right? And of course, we have our idea, our extension for business studio. 14:38.000 --> 14:40.000 And that's it. 14:40.000 --> 14:44.000 It's talking with the internal API, and you can do it if you want. 14:44.000 --> 14:52.000 And you can adapt for your rules, and for your wallpaper, and whatever you want. 14:52.000 --> 14:58.000 One of the things that we have to keep in mind is that the previous one, 14:58.000 --> 15:01.000 only works with Open API. 15:02.000 --> 15:08.000 But we don't have only Open API or rest specification in our company. 15:08.000 --> 15:14.000 We also work with ACing API, we also work with the ERPC. 15:14.000 --> 15:21.000 But in this case, we have an architecture to work with all of this. 15:21.000 --> 15:27.000 We also can work with GraphQL, and we also can work with events. 15:27.000 --> 15:30.000 And what kind of models can we use? 15:30.000 --> 15:34.000 Design, documentation, and security in the rest. 15:34.000 --> 15:39.000 But also, we have GraphQL, the only one that we are reviewing right now, 15:39.000 --> 15:43.000 it's GraphQL. So you can choose as you want. 15:43.000 --> 15:48.000 And again, this is the weight of each model. 15:48.000 --> 15:55.000 For us, the design is the 40% of the total score. 15:55.000 --> 15:59.000 No commentation is 15% and security is the rest. 15:59.000 --> 16:03.000 So don't forget that you can change, it is as you want. 16:07.000 --> 16:14.000 And again, with API, we can integrate this scoring in our tool. 16:14.000 --> 16:20.000 And this is a little bit of a little overview of our API portal. 16:20.000 --> 16:24.000 As you can see here, we're going to talk a little bit about that. 16:26.000 --> 16:30.000 As you can see here, we have our API. 16:30.000 --> 16:34.000 And on the top of that, we have the quality of the APIs. 16:34.000 --> 16:40.000 And if you choose one of them, you can see in an spider mode, 16:40.000 --> 16:46.000 how it's what is the total score of each model. 16:46.000 --> 16:54.000 So this is a good way to make some kind of public gaming too. 16:54.000 --> 17:02.000 To try to the people from all our business. 17:02.000 --> 17:06.000 Do the correct way that. 17:06.000 --> 17:09.000 And here you have, you can use the API. 17:09.000 --> 17:16.000 This is one approach that the thing that we can do with our API, right? 17:16.000 --> 17:21.000 What else? 17:22.000 --> 17:24.000 There we go. 17:24.000 --> 17:27.000 Well, no. 17:27.000 --> 17:33.000 In summary, we are working with better store always. 17:33.000 --> 17:38.000 We have evaluating all the things with three different tools. 17:38.000 --> 17:49.000 The first one is, it's one of the first ones. 17:50.000 --> 17:52.000 Great, my open API. 17:52.000 --> 17:54.000 And here we have one scoring. 17:54.000 --> 17:57.000 But the same jammer in another tool. 17:57.000 --> 18:01.000 We have a D, and we have a 61. 18:01.000 --> 18:03.000 So what happens here? 18:03.000 --> 18:08.000 And again, with the other one, we have also a C. 18:08.000 --> 18:10.000 So what does it mean? 18:10.000 --> 18:13.000 Nobody knows, but it's your score. 18:13.000 --> 18:16.000 But you can customize as you want. 18:16.000 --> 18:21.000 The idea is, well, what tool I need? 18:21.000 --> 18:26.000 Depending on the height of the company, right? 18:26.000 --> 18:36.000 So here you can see a little review of the things that we have worked in each tool. 18:36.000 --> 18:45.000 So the things that we review with, it's that regarding with the CLI, all of them has CLI. 18:45.000 --> 18:52.000 Regarding with the API, rate my open API, and in API scoring, you can use it. 18:52.000 --> 18:56.000 Inside, we have, and we are not able to do it to be honest. 18:56.000 --> 19:00.000 In the documentation, say it, but to be honest, we can do it. 19:00.000 --> 19:05.000 As you can see, the idea extension for this was to your code. 19:05.000 --> 19:08.000 We have insights, and IPA scoring. 19:08.000 --> 19:13.000 Also, regarding the weight paper, we can customize our rules 19:13.000 --> 19:17.000 that only in the API scoring. 19:17.000 --> 19:24.000 And again, the server site review, it's only do it by and inside. 19:24.000 --> 19:30.000 And one of the things that you have to give in mind if you are using another protocol, 19:30.000 --> 19:41.000 not only rest, if you are using, for instance, zero PC, there is no other way that API is scoring. 19:41.000 --> 19:55.000 Okay, so in summary, we have all of these things to know which one is better for your company for you. 19:55.000 --> 20:00.000 The first one, rate my open API is easy to use. 20:00.000 --> 20:04.000 They have my favorite one is the EA feature. 20:04.000 --> 20:11.000 You can be able to check if your API will be chosen by an EA to use. 20:11.000 --> 20:14.000 API insights. 20:14.000 --> 20:20.000 The only thing that we have to keep in mind in API insights is that we have server dependency. 20:20.000 --> 20:31.000 I mean, if you don't have a server up and running, we use on be able to score the API. 20:31.000 --> 20:34.000 And again, I'm sorry for that. 20:34.000 --> 20:41.000 It's, I don't know why, but they have an ABP for, for back. 20:41.000 --> 20:44.000 I don't really know. 20:44.000 --> 20:53.000 Well, and if you are in a big moment in your company, here you have the API scoring. 20:53.000 --> 20:55.000 We have multi protocol. 20:55.000 --> 20:59.000 That is one of the things that it's the most powerful thing that we have. 20:59.000 --> 21:06.000 And also, don't forget that we are able to customize over or over rules, right? 21:06.000 --> 21:10.000 And that's it. 21:10.000 --> 21:13.000 That is the, the review. 21:13.000 --> 21:15.000 I don't know if you have any question. 21:15.000 --> 21:16.000 And if not, sorry. 21:16.000 --> 21:18.000 Again, my apologies. 21:18.000 --> 21:21.000 We was drinking a lot yesterday. 21:30.000 --> 21:34.000 I forgot, but you can know a lot if you want. 21:34.000 --> 21:37.000 And you can use the tool by the way you want. 21:37.000 --> 21:39.000 It's a gift cup. 21:39.000 --> 21:40.000 It's a gift cup. 21:40.000 --> 21:42.000 I'm scoring. 21:42.000 --> 21:44.000 Any questions? 22:00.000 --> 22:02.000 Good question. 22:02.000 --> 22:03.000 I like it. 22:03.000 --> 22:08.000 We start work with a little PUC to know what is happening. 22:08.000 --> 22:16.000 But the solution that the, that there was already done for all. 22:16.000 --> 22:18.000 But we don't find. 22:18.000 --> 22:24.000 And we work in our, on our tool by yourself and forgetting about the other. 22:24.000 --> 22:28.000 After that, we take another review and say, hey, we are better. 22:28.000 --> 22:31.000 So that's, that's a point. 22:31.000 --> 22:34.000 Thanks. 22:34.000 --> 22:36.000 Yes, I'm on one. 22:36.000 --> 22:42.000 Since you use the tool yourself, is there any rules you have internally, so that the score is actually improved? 22:42.000 --> 22:43.000 Yeah. 22:43.000 --> 22:44.000 Or is it just a score? 22:44.000 --> 22:46.000 It never looks at it and it's D over time. 22:46.000 --> 22:47.000 No, no, no. 22:47.000 --> 22:49.000 We have a lot of, a lot of rules. 22:49.000 --> 22:52.000 And it's, it's, I don't know what is the folder. 22:52.000 --> 22:55.000 I think that it's, it's, it's rules that folder. 22:55.000 --> 22:57.000 And you can see what and, but we are doing. 22:57.000 --> 23:05.000 Again, we have, and a public rules, and also we have an internal one that we can share. 23:05.000 --> 23:08.000 That's a point. 23:08.000 --> 23:10.000 Tom, I was getting in and out. 23:10.000 --> 23:13.000 I probably have made a question that your video said something about that. 23:13.000 --> 23:20.000 So are you guys facing your rules in, in a spectral, just a spectral, or any other, of course, in all two? 23:20.000 --> 23:21.000 Good question. 23:21.000 --> 23:24.000 We are using a spectral, but also. 23:25.000 --> 23:34.000 We are working with, to work with Aradzo from now on, because we think that it's one of the ways that we have to, to keep in mind. 23:34.000 --> 23:39.000 Because, for instance, one of the things for Aradzo is EA. 23:39.000 --> 23:43.000 And another thing is stress testing and end to end testing. 23:43.000 --> 23:51.000 I think that it's a good tool to have in, in our rules. 23:52.000 --> 23:57.000 We use anything any tool for breaking changes detection. 23:57.000 --> 23:58.000 Good question. 23:58.000 --> 24:03.000 We also have our own tool for, to detect, or a big engine. 24:03.000 --> 24:06.000 But I can share right now. 24:06.000 --> 24:13.000 But we are thinking to, to make public with, with this project, you know, Panthers. 24:13.000 --> 24:15.000 This is a good question. 24:15.000 --> 24:19.000 Maybe we have working around one year talking about that. 24:19.000 --> 24:22.000 It's not, it's, it's, it's really true. 24:22.000 --> 24:25.000 And we have our tool to do that. 24:25.000 --> 24:26.000 Thank you. 24:26.000 --> 24:27.000 Thank you. 24:27.000 --> 24:34.000 And when you, your tool, it gives a great tool to the open up API, to the space, 24:34.000 --> 24:39.000 and so it's, like, a few hundred percent, but this, like, a test or not, leaving that, 24:39.000 --> 24:42.000 that I would, of, total out to be below. 24:42.000 --> 24:45.000 And what happens to do, do, do, do, do, do, do, do. 24:45.000 --> 24:49.000 Most features are gonna do them. 24:49.000 --> 24:57.000 So fragments of existing size ofing dorses. 24:57.000 --> 25:01.000 There's a'll type of, a little, a little, a little bit. 25:01.000 --> 25:05.000 I can't do that. 25:05.000 --> 25:09.000 Some are saying, perhaps we can't actually do that. 25:09.000 --> 25:13.000 So you can't do it this way. 25:13.000 --> 25:18.800 this laughing increasing or decreasing or what happens or maybe this payment get 25:18.800 --> 25:28.680 we are not working fine or whatever. So if something wrong happens, it's not our 25:28.680 --> 25:34.320 full. I mean it's a team who are building this API or this service who has the 25:34.320 --> 25:41.360 full. We put in the portal that you have for instance AC, it's not the best score 25:41.400 --> 25:49.960 for that. So up to you. We can't stop. We can be stopper for that. The business has to 25:49.960 --> 26:04.560 have to continue, so I think we are not stopper. So it's only okay, what is happening? I don't 26:04.560 --> 26:09.880 really know, take a look at your API, you already have a scoring an F, why are you 26:09.880 --> 26:19.600 going out? Well, you know, it's just your fault, you know? Yeah, of course. In certain cases when the 26:19.600 --> 26:24.520 scoring is below something or in a certain category, it's not, it's not, not really 26:24.520 --> 26:28.320 stop, it's only a warning, but we can configure for for a stop. It's only a warning and 26:28.320 --> 26:37.000 you can say, hey, this is a warning, up to you. Any questions? So thank you very much for your 26:37.000 --> 26:38.000 attention.