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