00:00:00.480
okay so call it what you will we tend to use
00:00:05.580
the phrase API consumption it's all about calling apis primarily HTTP apis
00:00:12.660
if you want to use the phrase rest apis that works too uh we are trying to make
00:00:18.359
it easier for people to call HTTP apis and you'll sort of see in a minute why
00:00:23.699
that's important to us um so we're starting to build a little bit of a montreal-based team uh Vincent
00:00:30.300
who actually arranged this thank you business but anyone who got married in Mexico right now and he said hey
00:00:38.520
sir Daryl could you go to this thing in Ruby and certainly I kind of looked at
00:00:43.800
each other okay sure yeah whatever no problem
00:00:49.800
um and so that's the three of us who are based here in Montreal uh but the team that are working on this set of tools
00:00:57.120
children and product to access apis is all over the world we have a PM that's
00:01:02.640
based in England we have a team at devs in Nairobi we do have some devs in
00:01:07.740
Redmond but you know we're kind of all over the place so to your question earlier we work from
00:01:15.060
Montreal but not really in in the Montreal office once every six months we'll go into the
00:01:21.540
exactly Isis like earlier today before we came here using our advantages make sure that they still feel this way
00:01:30.680
so the actual team that we work on is um
00:01:36.720
the developer experience team for you know call it a product called
00:01:42.000
Microsoft graph have you ever heard of marks okra do you know what that thing
00:01:47.040
is are you using teams at work sometimes
00:02:07.340
everything that facts teams and office and SharePoint which is where we store
00:02:13.260
files and uh emails and all click and everything all of that is stored across
00:02:19.280
thousands of services and databases and whatever but it's all available through
00:02:25.440
a single API that is available within Microsoft and we are the ones empowering devs to
00:02:33.180
connect to basically any pieces of things out of things in their like Enterprise database that is also by
00:02:41.280
Microsoft so because we're like we're building tools for for that team to
00:02:46.800
access data inside Microsoft because about age or nine years ago it would be
00:02:52.200
you went and used a long drive or you went and used the SharePoint issue or you use the exchange API that was all
00:02:58.500
managed by a different teams presented documentation at Egyptian set of sdks and everybody just think kind of
00:03:04.440
differently and to get a token for each one of those and it was a pain and so it was actually
00:03:09.599
um the people who were working micro field sales were like you need to fix the ship because it is a mess and it's a
00:03:16.620
nightmare getting people to integrate the stuff and so Microsoft graph was born as an umbrella and really we are
00:03:22.920
just a proxy we're just a oh cool term of the Year Federated Gateway
00:03:29.840
to all of the underlying Services um just so that there's a consistent
00:03:35.459
developer experience and all of that data that's stored in the Microsoft cloud gets exposed but it ends up being
00:03:42.540
an API surface area 22 000 operations across the whole APS
00:03:48.780
surface area which causes some challenges with certain tooling when you're trying to use it so one of the things our team builds is
00:03:57.299
a bunch of sdks and a bunch of different languages and we're fairly successful at growing
00:04:04.560
the use of rsdks we've got more than 500 000 applications out there going and
00:04:10.080
calling Microsoft graph API to do various things we've got some good growth we've got growth across a bunch
00:04:15.480
of different languages Ruby is in there somewhere but we have a ruby SDK that
00:04:22.800
has been had it's just no love quote for quite a number of years because we
00:04:28.380
haven't had any devs on the team who actually knew how to use Ruby um and so but we do actually have some
00:04:36.479
usage of it we have a lot of growth billion requests a month like using RSP
00:04:43.320
cameras and starting to get a little bit of hockey stick we're getting good growth it's great
00:04:48.419
until you look at this chart where the green is the stuff used in usdks and the
00:04:54.960
purple is people just calling the HTTP API directly a lot of people just like don't use
00:05:02.340
rsdks hurts yeah curious here so you're
00:05:08.220
building mainly I guess in the ocean in some other languages
00:05:13.520
away what's your feeling about asdk do you do you like using an SDK a
00:05:21.120
library that kind of abstracts the complexity of an API for you or you're
00:05:27.300
like the warrior and it comes in hey I know how to do it I know how to do it it's easy yeah it's that resource
00:05:33.419
passing in a bearer token boom access and then yeah what if your needs
00:05:39.840
is in your mind before deploying the risk is that it should be
00:05:45.180
simple you know I just need this so I'm a very basic thing maybe just a call you know you're in
00:05:52.259
your python or Ruby world so just call that http get an adjacent resolve and
00:05:58.080
that's it but your question is also okay if if there are some that would say a behavior
00:06:05.220
of uh content and maybe library's maybe something tricks that I don't know because you
00:06:12.300
know it's a new field maybe I want to be well taken care of maybe I would like to
00:06:19.220
something a little more advanced so it's suffocated look at tutorial trying to figure out what's going to do for me you
00:06:25.979
know doing what I need cool I'll just import it download it package it whatever yeah and then I'll use this yes
00:06:31.919
awesome are others feeling the same but maybe as many people are using
00:06:40.319
I don't know the exact results about it yeah maybe they're using Legacy software
00:06:46.020
they're just some dating it day by day and they don't want to go around
00:06:51.500
so you don't touch or whatever is there so maybe you're using it SDK and you don't like it because you're in an old
00:06:57.240
code base or you're not using an SDK because you you don't like it because you're also in that old pull-based
00:07:03.479
buildings or whatever yeah that's what we're using it doesn't
00:07:09.500
what we do we do have an SDK project we built our own
00:07:15.500
modules yeah because it's like because of migrating our stuff
00:07:21.300
like that that's been expensive but why is we will do it if we already have one
00:07:27.360
yeah how many sdks you might take it
00:07:33.060
5 10 100 maybe yeah there we go
00:07:38.400
so why do we care about people using sdks well we spent a while in the space
00:07:45.060
and we found people run into a bunch of issues so we've built stuff that makes it easier to do all because getting the
00:07:52.259
token is usually one of the hardest parts obviously call it an API um over on Microsoft graph world we have
00:08:00.060
started to have some Advanced capabilities where admins can control access to a variety of things and make
00:08:05.940
sure that you're doing multi-factor authentication and we handle all this kind of advanced all type scenarios in
00:08:12.419
rsdks so people can get on with just doing the business that they're trying to do and not worrying about all these
00:08:18.720
fancy new security things retry handling you know people with hammer apis and end
00:08:23.759
up returning a 429 and we do the right thing return retry after headers that say how long you should wait before you
00:08:30.120
try again and our Appliance staff libraries do that you know serializing and deserializing the payloads for the
00:08:37.080
most of the time is fairly and forward until you get adjacent payload with a date or duration or
00:08:43.500
very large decimal value or a decimal where you care about the Precision there
00:08:48.959
starts to be a bunch of edge cases when you have things where you're using inheritance or and you have polymorphic
00:08:55.680
collections this gets harder we take care of a lot of these things so we have found that by developers using the sdks
00:09:04.080
they can build apps movable get to Market faster and you kind of stall my thunder on this
00:09:10.620
yeah sorry actually this is my this is my how do you feel about sdks and what
00:09:15.779
I've found is like there's people who either love them or they hate them right it's kind of like I won't use your API
00:09:21.300
unless you give me an SDK or yeah get up on the plane I don't know how to make http
00:09:30.560
We're Not Gonna Be Friends so over time you've really identified a
00:09:37.080
bunch of things why people don't like using SDK so I don't need this because I know how to do it so
00:09:44.220
I don't want dependencies dependencies can be a real thing especially when you start calling multiple apis through your
00:09:50.339
application because that SDK pulled in some dependency library that one pulled
00:09:56.040
in the same library but a different version of it now there's conflicts of it there can be challenges people can
00:10:02.399
struggle to find sdks because it's like well where do I go looking well okay maybe you can go looking on your package
00:10:08.580
manager uh and you can find it but is that the official one or is that some kind of like Community developed one
00:10:16.260
um performance people are like well they're not too sure about that SDK was it
00:10:22.200
written efficiently is buffering item there did somebody know what they
00:10:27.720
were doing or did they just use a code generator and spit out garbage right because they were just in a hurry and
00:10:32.940
the boss told them go generate this thing in seven different languages
00:10:38.459
um because this is the problem that's making a provider you don't just have to support one language you got to support
00:10:43.980
a bunch of languages for the broadest audience we have a unique problem of having 22
00:10:50.700
000 endpoints is that our package gets kind of large you can talk to Seth
00:10:55.980
afterwards about how large are typescript packages that we probably will never ship because
00:11:01.620
of how big it is um some people don't realize the value that
00:11:07.200
it's bringing yeah it's a Marketplace and quality is definitely an issue there's a bunch of not very good
00:11:13.040
cogenerators out of there there's also a bunch of challenges with code generators often will work off an API description
00:11:19.800
there's a lot of low quality API descriptions out so there's reasons why people don't want
00:11:25.260
to use sdks but then there are people who absolutely do want it and I want to walk through a little bit of a scenario
00:11:31.380
of one of the popular apis today and sadly it's called open AI so I'm gonna
00:11:37.260
have to say the words open Ai and open API all together a few times it's hard work good luck
00:11:44.100
um so open AI everybody's into chat GPT and all the things I want to go and and
00:11:50.519
call it and integrate these great llm capabilities into my application they've got a really nice developer portal and
00:11:56.880
you can they show you how to do it you can learn a lot of things about how to call chat GPT from this API and if you
00:12:03.899
want to build your application they've got sdks in node.js everything else is like this Community
00:12:10.200
Library go figure it out yourself now they did provide an open API description
00:12:18.300
and so you can go download that open internet description and you can feed it to a code generator so that it will
00:12:23.940
generate an SDK for you in fact that's actually what they did for their typescript
00:12:30.920
no the type of the heavy coded the JavaScript one they generated
00:12:36.720
because all the machine learning folks are all the python Cruisers um so they went and used open API
00:12:43.440
generator which is one of the most common uh generators out there um
00:12:49.440
but it doesn't work so then they wrote a bunch of scripts that would take their open API
00:12:55.740
description and fix the open API description because open API generator has a bunch of scenarios that doesn't
00:13:01.320
really support and so it just becomes complicated okay fine it does generate and it will work
00:13:09.120
if you're working in a fairly Dynamic type language because the way that open
00:13:14.639
apis describe their API especially when you're doing prompt completion they have this little description here using
00:13:20.760
adjacent scalable and they say if you want me to do a prompt completion you can send me a string or an array of
00:13:27.959
strings or or an integer or an array of integers well if you're a code generator
00:13:34.200
trying to generate that in Java or C sharp it's not the easiest thing because
00:13:40.680
it doesn't have Union tires and so most SDK generators will not be able to
00:13:45.839
handle this so what's the good developer to do well maybe else has gone and built something
00:13:51.660
so I'm going to go to my package managers I'm going to nougat and I'm going to go if I'm a C sharp developer
00:13:57.660
and I'm going to search for open89 fortunately I have a luxury of many choices of 37 different packages to
00:14:04.800
choose from which one am I going to pick there's none of them are official no idea how long somebody spent we don't
00:14:11.459
know which ones of those are doing Bitcoin marketing inside it right how long you know whether or not it's ever
00:14:17.279
going to be supported and it's not just in the C sharp world if you go to npm and search for opening API there's 60 on
00:14:23.940
packages there they even have an official one there's still another bunch of them so it's like you're like oh
00:14:33.440
dependency that's going to go sour I don't have to ah it's not a very big API there's only
00:14:41.399
those few endpoints I only need to call some of them all right I own right and
00:14:47.519
then we've got another one I can just just it's just calling HTTP I know how
00:14:52.800
to make HTTP calls and the happy path of making HP calls yes is a fairly happy path it's not too
00:14:59.699
bad edge cases that come back further down the road when you deployed the app into
00:15:05.339
production and something goes wrong and you're like I wish I had something a little bit more robust and more
00:15:11.820
resilient because I just didn't have time or it's not my
00:15:18.360
area of expertise I know how to do a basic call but I don't really know how 429th or or what a 202 means a what a
00:15:25.380
407 means right so this is where we are trying to help
00:15:31.560
out here we're trying to help out API consumers consume apis because
00:15:36.600
traditionally the role of honest having an SDK is a
00:15:42.540
burden that we put on API providers I've got an API I want all the people to come
00:15:48.060
use my API because I think it's awesome and I want to get customers and I want to reach the wireless audience so now I
00:15:53.579
have to produce sdks in all of these languages but I'm going to produce a bunch of sdks
00:15:59.399
they're not quite the same as another another API who produces what your sdks and so
00:16:06.120
there's that resistance and like you saw our numbers like we're a team that have spent a lot of time with sdks and we're
00:16:13.320
only seeing 40 of our customers using our sdks even with their effort that we
00:16:19.500
put in and I've talked to people at Google I've talked to people at GitHub our numbers are no worse than anybody
00:16:26.519
else's when it comes to adoption that's the case yes numbers are real because because Legacy
00:16:32.279
work that came before you or you're starting from a certain date they say
00:16:37.920
we're available and still people are not using so the 40 is 40 of new
00:16:44.339
applications so every day people are creating new app in the in our portals yeah they get a an
00:16:53.160
ID and a key and 40 of them are using vsdk 60 of them
00:16:59.399
are not and we have a team of people looking at our portal trying to optimize
00:17:04.500
our paths to get people to drive take them down the happy paths like we've we're funded to do this and yet there's
00:17:11.400
still a challenge there right there's still that resistance and it causes people to go build stuff
00:17:16.919
so how do you solve the problem where there's all these different options that
00:17:22.860
you don't like anymore you go build another one we built a new code generator oh that's the wrong way I want
00:17:28.260
to go that way and this is just kind of a high level of
00:17:33.780
the way we think about the way we do code generation we are building it off open API because we went through a bunch
00:17:40.860
of years of API description Wars and the war one an open API basically one as a
00:17:47.120
description format for interoperability there are better languages API design
00:17:53.340
languages out there for Designing but as far as interoperability open API works
00:17:59.340
we'll take VT V2 V3 hopefully very soon we'll support V 3.1 the animal Jason I
00:18:06.299
don't care whatever you want Pull It in we take that set of URLs in the API we
00:18:12.780
build a tree out of it there's a lot of other code generators
00:18:18.240
who have tried to take the list of operations in an open API description
00:18:23.640
and try to create a bunch of methods on the class and it doesn't scale and it
00:18:28.740
requires developers to go and fill in the operation ID so first of all I designed my API and then you want me to
00:18:35.220
go and give a bunch of new names so that you know what to do coaching we don't we use the path structure that hierarchy
00:18:42.840
and that works well for us with graph because we are a big surface area
00:18:48.240
you'll see what we mean by that so if we build the URI space and then we create a code guide a lot of code generators out
00:18:55.320
there we'll try to use templating as a way of doing it Templeton has its pros
00:19:00.900
and cons we used to do templating you know the kind of the mustache templates approach but it actually causes a lot of
00:19:08.400
Maintenance work s um and we it ends up pushing a lot of
00:19:15.059
logic into the terms of sort of specific two particular languages which becomes a
00:19:20.520
maintenance burden so we build a code model based on what we generically think
00:19:26.160
our SDK should look like what classes should exist what properties and methods and then we refine it by model so that
00:19:33.299
we're using the features of the language in C sharp we make sure that we use indexers in go we go well I guess we
00:19:40.559
don't have inheritance so we'll figure out another way of doing it we use the capabilities of The Language by refactoring that code model and then we
00:19:48.240
just pass it on to what we call language writers so the particular language writers just take the code mod and
00:19:54.600
they're writing it out and we package all this up in a fairly straightforward cross-platform single binary you can
00:20:01.500
download it in a Docker container you can download it as a cross-platform exe you can download it using regular.com
00:20:08.039
but it works anywhere and it's fairly low impact
00:20:13.679
but the code generation is only one part of the story let's look at how it fits in to your
00:20:20.820
overall applications you have your application
00:20:26.580
and you want to call our generated Kyoto API client code and we have a pretty
00:20:33.960
opinionated way that we project out that HTTP API service area we don't try and
00:20:40.260
minikits the most perfect API surface area possible we'll try and make it as
00:20:45.960
consistent with the API as possible and is predictable because as we're discovering in this world of co-pilots
00:20:52.740
and llms and generated stuff predictable this has a lot of advantages
00:20:57.840
but we also don't recommend that you if you're building an app that you put our code
00:21:03.720
all the way through your code base build the service adapters go to service adapter over our code it
00:21:10.140
allows you to configure it set up your Telemetry if you're using open Telemetry do all of that necessary configuration
00:21:16.020
and isolate our generated code from the rest of your application okay now we've
00:21:21.179
got the generating code because it figures out how to make the HP requests does all the serialization all that
00:21:26.220
stuff it builds on top of a bunch of core libraries the only one you really need
00:21:31.919
is kill abstractions which describe defines this interface layer between our
00:21:37.380
generated code and the native code that is calling the underlying negative HP
00:21:43.380
libraries so in Ruby we're using Faraday at the moment if you want to use a
00:21:48.659
different HTTP client Library you can build replaceable core libraries if you want to support other media types you
00:21:55.559
can build your other serialization libraries if you have some weird authorization model that you want to do
00:22:01.500
you can plug that all in it will all just work but it's that stuff then allows you to call
00:22:08.400
an HTTP service any HP service in a fairly standardized consistent way you
00:22:15.780
learn it once you can call any API describe an open API
00:22:22.020
now this is not a new idea this idea of having consumers generate code in order
00:22:29.220
to be able to call other services we've never really done it for HTTP for some
00:22:34.260
reason we took a different path we expected API providers to go do the work but if you work in graphql you
00:22:41.640
don't go oh I want to go and download the graphql SDK for GitHub just go download some graphql quiet side tooling
00:22:49.380
and it can call any graph as well API if you want to call grpc you can go to Chronic C grab the Proto schema generate
00:22:57.539
a stub boom and I usually get some moves and misses when I mention this but
00:23:03.240
that's how I did it and so too you pointed to a whistle and we generate this stuff and you can
00:23:09.600
make a call but there's far more htcp apis out there
00:23:14.880
it's been there are the other protocols and so this is where the biggest
00:23:20.100
opportunity is just to summarize for a second
00:23:25.679
why are we doing something different because there are other open API there
00:23:31.020
are other code generators based off the open API that arouse them
00:23:36.360
a who focused on the consumer and what we discovered when
00:23:42.419
we started focusing on the consumer as I mentioned it before it's way more than
00:23:47.580
just generating the code there's a whole experience around I want to go call it
00:23:54.360
AP first of all you've got to discover that API analysts open API description that in itself is a challenge so we
00:24:02.039
built tooling to go searching for open API descriptions and we've got a bunch of different techniques is how you can
00:24:08.220
find the open API that you need we also recognize is that
00:24:13.980
people don't consume apis in the same level of granularity
00:24:20.460
as the way people publish them with the team that publishes it says here's the set of functionality that does this set
00:24:26.880
of things that might be useful to you and use the consumer bill I want that and I want that and I don't really care
00:24:33.419
about the rest of it at the moment I only care about those things why should I generate code for the whole surface
00:24:39.960
area what I normally care about those so we built tooling that allows you to just
00:24:45.000
generate the code for the forest that you care about now go back to Microsoft craft when you've got 22 000 endpoints
00:24:51.780
nobody calls them all and you have size problems so if you can just pick the ones that you want you don't have size
00:24:57.900
problems anymore we don't even install them we don't know what all of them are
00:25:03.840
exactly they're all finished um open API support I'm a little bit of
00:25:09.000
a developed on this particular topic I've worked since 2016 on the open API technical steering
00:25:16.919
committee so I contributed a lot to open API V3 we're currently working and okay
00:25:24.260
3.1 we're currently working on it we need the IV uh code name moonwalk
00:25:30.179
because nobody likes open API and everybody still calls it Swagger so we figured well if we point with a new name
00:25:36.360
it's cool maybe if you want to stop holding the Swagger um
00:25:41.760
so we are very fixated on making sure that we
00:25:46.980
accurately represent open API descriptions support all the features and generate as accurate as possible
00:25:53.299
sdks from that open API description I mentioned about the fact that we built
00:25:59.940
this URI space rather than me try and describe it it's better if you just see it in the demo as
00:26:05.520
to what we mean by that and last but not least some people like this point some people
00:26:10.919
don't um and especially because we are a completely open source project we are
00:26:17.400
I'm gonna say wait are we Apache or MIT I think we're mites that might say all of Microsoft stocks
00:26:23.820
we are on Microsoft GitHub or we are MSA license we have had a bunch of
00:26:30.179
contributions from external people red hat and now contributing extensively right now we're going to use this for
00:26:35.760
their Cloud sdks um and we intend on building the community we're in conversations with
00:26:42.120
GitHub GitHub need to support some of the languages for their API so they're trying to get out at the moment
00:26:47.900
we need sdks for our Microsoft graph customers we have a team building it
00:26:54.179
across these languages yes we don't have something with Ruby skills and I absolutely wish we did
00:27:00.120
um but we're learning and this is another good reason why we're here because we need feedback on our our Ruby
00:27:07.500
Generation Um but we're not going away
00:27:12.860
this tooling is going to need to exist for Microsoft and we are absolutely
00:27:18.659
committed to it being an open source effort that accepts external contributions not just a source open
00:27:25.380
effort and with that I'll stop talking and he's going to try and show Rubik's
00:27:31.860
head 31 minutes without seeing a code my eyes are deleted
00:27:36.900
um slides are boring no I'm joking uh I hope you like the story do you mind if I stay in English I don't know the flow is
00:27:43.140
just more natural I do I get everybody is everybody speaking French
00:28:10.460
yeah but that's okay um as I was talking about
00:28:15.659
being an API consumer first kind of thing product technology
00:28:21.320
approaches and I'm going to ask you this where is a developer spending their
00:28:29.100
entire day in their goddamn IDE right they spend
00:28:34.679
their time coding I can bring you to a portal I can build
00:28:40.080
you a nice ass I could those are all things that will distract you from being productive as a Dev
00:28:46.679
that's why you have so much tooling and when you commit to an idea or to a
00:28:52.740
technology you make sure that okay there I cannot I don't want to notepad plus the last type of experience when I code
00:28:59.460
even though I did that when I was younger and I thought it was cool until I kind of learned what the world was
00:29:05.400
about and oh my God I can dot something and I can see what's available in that
00:29:10.500
object and and that's cool I'm cool Pilots second that's how I learned my Ruby
00:29:17.580
skills co-pilotism is a great virus still big big big cabin
00:29:25.220
we as Microsoft the technology we're building which is kyota is built in the
00:29:32.820
language of choice of Microsoft it's the language we we have uh the most knowledge about it's definitely we're
00:29:39.720
building it.net into C sharp for you like you don't even need to care about what's detect that is behind it unless
00:29:46.320
you want to contribute to it and it's a great learning opportunity that's what our folks at Red Hat have been sharing
00:29:51.960
with us because they're not writing in that absolutely keep in mind.net today is 40 plus across platform Linux Mac or
00:29:59.820
Windows you can run it on PS code that's what I'm going to do today um so but we want to to reach the devs
00:30:07.740
where they are when we look at the numbers today even though some languages have great support
00:30:14.659
okay support vs code is where a lot of developers are spreading they are I'm
00:30:20.940
curious I'm going to ask you the reasons what are you using in Ruby to code so vs code
00:30:26.720
okay cool okay so the okay that's that's the the
00:30:33.000
other one um well maybe like in the in the compete space
00:30:38.880
um we're trying with with we're starting with vs code everything we do is actually part of the kiodesk like the
00:30:45.960
CLI we build so actually plugging into where there's our building could be something that that we think um in the
00:30:52.380
future in the future um so if we say that we live in Via Stone
00:30:58.200
that the devs are there that the tooling is there and why not build for these
00:31:04.260
folks right um so let's go on and open up we have an interest in terms of someone who's going
00:31:10.980
to try to build an intelligent plugin and Delhi and there we go so there we go we're going to extend that some of that
00:31:17.100
so let me close that thing here some close teams still think that there's nothing in the
00:31:22.440
thing popping up on my screen uh and let me open up that um
00:31:32.820
VM here that runs somewhere in in the cloud
00:31:39.179
um why I'm building it I'm running a VM I swaps up like four laptops a day so it's just easier to have that one thing
00:31:45.840
so I don't have to build everything all the time let me close that
00:31:57.720
it's okay sometimes I switched to light yeah
00:32:03.840
um it usually um in presentations we should be using light
00:32:09.539
um to small room so I must not I'm not too scary we're leaving so where do we start I wanna
00:32:16.980
learn about kyota by the way I'm recording these like this light better for me no it's it's going to be okay
00:32:23.279
it's gonna be okay um so I'm here I'm in my machine I run this
00:32:29.580
on Windows I'm actually not on Windows you can see here on you I'm running it through double ESL the windows uh it's
00:32:36.899
obsessive for Linux so I'm in Linux I have vs code open and I want to figure
00:32:42.840
out what kilo is all about so as a Dev my first thought the thing that I did I
00:32:48.240
shoot for Ruby I was like so we had to talk we want to meet the the Ruby devs
00:32:53.940
where where do I start I go in the extensions in VSCO in I type Ruby then I
00:32:59.159
got a little bit confused about all the ways to get intellisense and debugging and everything I ended up with the
00:33:04.200
Shopify extension is that the best one that's I don't know like the one that like provides all the really cool
00:33:10.559
intellisense and running debug whatever also complete yeah you tell Hisense is very visual studio
00:33:18.120
um so that's why my search might have not really do the best thing so I'm gonna go here I'm gonna search for stuff
00:33:24.659
I'm gonna search for kios and then I find that one extension
00:33:31.080
which is the Microsoft Toyota where you have all the description here it's already installed you install it what it
00:33:36.659
does it does two things it installed the extension so basically a UI
00:33:44.100
add-ons in some areas of vs code and it also installs the CLI so the tooling to
00:33:51.480
generate code inside vs code so as there's like a map folder somewhere it
00:33:57.059
installs it there and it tells me at the bottom that I'm using the Q10 1.1.3 version
00:34:04.159
which when you come back to us and you say your stuff is perhaps uh it's it
00:34:09.899
broke my code we're going to ask you for that uh so that's why we used to write it actually
00:34:15.899
um
00:34:30.780
three seconds and now I have a new kind of crafty I call them right here it's
00:34:36.480
Cuba welcome to Kiana um
00:34:44.280
we start there the first thing that I said earlier is dads have a hard time to
00:34:50.339
find apis I have a hard time you guys when you're building tools in the open
00:34:57.060
API space I can tell you that sure sure finding open API descriptions that are valid well written
00:35:04.200
that are a natural representation of the real API is a challenge so we're like we
00:35:12.780
can believe all the debt needs to go through this if we need to go through this so we're going to build something really cool because there is no npm and
00:35:20.579
JS equivalent for it yes there's no nougat there's no made in central there's no equivalent but imagine if it
00:35:27.839
was because then we could have one for all programming languages it wouldn't matter if programming we just all have
00:35:33.839
one and that's the beauty of apis apis are language agnostic right it's
00:35:39.119
a URL an HTTP endpoint and you call it in your in your ads even for somebody
00:35:44.460
that does not want to have to like generative code having an idea of what the API looks like is not a bad idea
00:35:51.599
so let's start with search and is it big enough in the back yeah it's good okay
00:35:57.839
um
00:36:24.140
do we agree with the policy or we don't uh but I've never searched this before
00:36:30.720
I know it's there oh you didn't so currently yeah there's a V1 of the API
00:36:37.560
there's the current so I found two apis there's the V1 there's the V2 there's
00:36:43.560
some description there's the description if you want and cool so uh
00:36:57.980
I just want to connect to the API I don't even know what language I'm going to build let's say every day you come to
00:37:04.020
work you're like I'm gonna go relax I'm gonna spin a big wheel and it's going to select the language for me okay let's do
00:37:10.680
that it's HP day it's PHP it's uh pearls it's been a while I've been coding for
00:37:18.180
um I clicked on the API and then it opened up a tree
00:37:24.560
yeah so am I gonna do this I can go okay so there's a couple of ones
00:37:30.240
um in in the URL segment now I have okay I have compliance definitely Twitter must not because
00:37:39.780
you did a search and yeah so so q9 is plugged into
00:37:47.339
um different search providers we use a first one which is a portal called API
00:37:53.339
gurus which is a vetted set of open apis 2500 approximately open
00:38:00.000
apis that are vetted confirmed valid
00:38:05.339
um we also use GitHub so basically anybody in the world could create a repo
00:38:12.359
tag the repo at the topic um index on on their repo and we're
00:38:18.240
going to search for an API that Json on that repo so what is a cool thing is everybody can
00:38:25.320
publish that it's using GitHub so zero gosh I do that I go through PR mechanism
00:38:31.020
I update my thing based on the updates in my API but also we provide the
00:38:36.660
capability to do that for private design so you can log into the tool with GitHub
00:38:41.700
and then you can do that in your private GitHub videos you're using GitHub private to do some stuff
00:38:47.520
um so depending on the organization like everybody has different things but nothing will prevent us for example to
00:38:53.040
build a get lab uh connection a Azure devops connection a whatever the tool
00:39:00.599
you're using we could do that so I clicked on it I basically in the API of
00:39:06.599
Json there's a link to the open API and I load it basically we have libraries as
00:39:12.119
we build and cars that horrible I hate you who loves me
00:39:19.339
yeah bad audience I guess uh I'm a Jackson
00:39:24.780
died yeah I know I know I know I've I've been
00:39:30.000
through this I I was in the PHD space before though I'm filming Symphony
00:39:36.240
um so it opens up their creative truth
00:39:41.579
so think about it when you do an HTTP call straight to the API what would you
00:39:47.760
do here you can already see it almost like a documentation right
00:39:53.640
I don't have that version loaded up because but now we actually have as an open API
00:40:00.480
there's actually an option to provide prescription and then the
00:40:05.700
documentation yes so now you actually would be able to click and get online click through this
00:40:11.460
specific method get the documentation by the API provider so from a new pad provider
00:40:17.400
there's no cost if anybody can become a nuclear provider or you generate your open API and then
00:40:22.740
you don't need to generate all the sdks because the consumer as well as like everyone right now let's say interested
00:40:28.020
in tools and I'm interested in uh the fire hose I'm going to get a
00:40:34.740
streak so here I could do this I'm like I really like Twitter I'm gonna go up I'm
00:40:41.520
gonna add them all now I basically generated the SDK or a
00:40:47.640
library that connects to everything in in Twitter
00:40:54.660
what I want to do is just a straight line if that's the only thing I care about my boss asked me I'm gonna have to
00:41:01.320
stream of all the all the Tweets in Twitter
00:41:06.660
as a background on like a TV on like you go at the Twitter HQ and you have all
00:41:13.020
the tweets and it's just clicking the fire emotion pretty fast yeah I don't
00:41:18.300
think it's any useful but hey maybe maybe Ellen loves to see all the tweets okay
00:41:26.060
like and that would be an example of how we manage 429
00:41:35.660
identified the pieces of the API that I care about um I'm gonna go on I'm going to hit play
00:41:43.520
oh I'm very very cool let's see how it works now it's gonna ask me you want to generate an API
00:41:50.579
client for this yeah okay how do you want to call it I want to call it Twitter
00:41:56.280
client I want to call it I don't know I'm going to call it within Twitter
00:42:04.380
um let's put it in Twitter in a folder called Twitter and then it's just going to generate all the code
00:42:11.099
and all the HTTP stuff and everything is part of that package it's going to
00:42:17.640
rely on on the on our abstractions our implementation that we provide by default or your own if you want to rely
00:42:24.660
on your own I'm gonna do that and it's going to ask you okay cool this is where the roulette starts
00:42:33.540
um uh what do you want to do do you want to do C sharp this is the only one that is
00:42:39.420
stable but you won't be able to read it right and it's going to be fun you won't know if it actually works
00:42:45.900
um I never missed it but I mean I can read it I think everybody can if I have no job if you're if you can read
00:42:53.220
typescript you can see each other even like yes today but
00:42:59.460
let's go where we are let's do Ruby yeah yeah right
00:43:05.099
and now this is where we never know actually like generations of 25 implied
00:43:13.319
for Ruby at and it gives me the password just creating it thank you that's it let's do it have a
00:43:19.859
great day everybody we're not showing you the code
00:43:26.060
so let me go back to my Explorer well now you see this I have I don't know a
00:43:32.220
very bare bottom this is probably tons of back practices in Ruby I just want to I think the goal
00:43:39.480
is not to show you how I'm good at writing Ruby the goal is to show you how good we are as generating Ruby code that
00:43:45.780
you can put in your super cool app this is the value is there not our all right so we have Twitter so what do we
00:43:52.619
have in here we have one thing I love how it translated to to because
00:44:00.060
some languages does not support using um
00:44:05.660
so first the queen of the client in there and you see it's it's proper
00:44:11.640
Ruby code and in there there's initialize and then you're going to find it too method
00:44:18.180
so you're going to be able to do client Dot two then afterwards is gonna
00:44:24.480
do a 2 what does it look like
00:44:31.140
does it look like the URL pretty much looks like the URL right so except like a two yeah but when you're
00:44:39.720
going to use in your code you're not just going to call get all stream tweets or get all tweets
00:44:47.220
from stream no you're gonna respect the API structure and that's a key to why
00:44:54.240
when you you maintain 100 sdks like I'll have different maintainers different
00:44:59.280
Fashions this year this pattern was cool the next year this pattern was not cool
00:45:05.760
so now you have 100 sdks to maintain well this all your sdks are exactly the
00:45:11.760
same the same thing you would be using just by using you should be endpoints but you're using that then you can go to
00:45:17.280
the tweets and then the tweets you're going to have the fire hose and then the firehouse you're going to have a stream and then the stream you know have
00:45:23.280
the stream that you're going to have to get because you're going to do a get on here streaming
00:45:30.240
so that's what we do we generate just the pieces of an API we line everything
00:45:36.180
up together we create the structure we make sure that it's properly created you don't
00:45:41.940
have to think about this code we even have questions around should you commit this code
00:45:50.220
why because actually as part of the generation we just created something
00:45:55.500
called a q a lot file that killer that file is this
00:46:01.740
this and where the description is what's the hash so basically if it
00:46:08.880
changed we're going to know that it actually changed and only if the methods
00:46:14.040
that you selected change do we care about it so some of the things that you don't use change they won't do a region
00:46:20.579
exactly and then at the bottom you're going to see oh the include patterns we're using glove patterns to give you
00:46:26.760
so that's the pattern that we care about in the URL we and then you could regenerate and
00:46:33.720
regenerate and regenerate the same code will always get generated so your code that is that you're you're using will
00:46:40.560
never get broken especially if you put the facade on top of it you're a service adapter something that has all your your
00:46:48.660
business uh best practices in there then we're good to go
00:46:54.359
so so the goal is to to have like say functional code that works yeah and then
00:47:00.359
you're happy in you with the last what you just you just quote was it you know it's going to update itself in some way
00:47:07.319
yeah how many people are playing on changing that code based on your experience that go into
00:47:13.140
that code and kind of fine tune it or something it's not nobody said we do not so our recommendation is don't touch it
00:47:19.200
yeah okay anything you're going to do there next Generation we're not even looking at it
00:47:25.079
if you if you tell me you regenerate we're gonna reach it we're not doing this yes uh yeah you guys can even
00:47:32.160
improve further on that code if you follow the rails conventions of translating um rest apis into show update delete
00:47:40.260
create um index yeah that would be even a higher level of
00:47:46.619
abstraction what we've talked about doing is adding hints into the open API
00:47:52.500
description so if you have a gap method you can put a hit a client hint that
00:47:57.780
says when you go generate the the final method on the end of the path don't use
00:48:03.119
the word get use this word instead but interesting sure interesting for Ruby
00:48:08.940
looks like there's a convention but it's it's so right now we're really focusing on HTTP so HTTP is get whatever it is so
00:48:18.420
so that's a very very good thing and I think this is exactly like a feedback you want to hear from from you is
00:48:25.440
will this look ridiculous across the rest of your of your code base or
00:48:32.339
remember this is commodity code it's code you don't really want to make code
00:48:37.440
you don't really want to write officially and it's code that even you might you never come into you might
00:48:42.540
never see that real code you're going to see the the projection of it when you're going
00:48:48.660
to call it but the actual code is not that right so let's do a real estate arm so I didn't want to test it on the
00:48:55.380
Twitter API because I don't have 149 bucks to spend tonight but uh and still
00:49:02.099
eats this let's go back and let's and you don't
00:49:07.800
need to delete you can have as many sdks side by side oh yeah I'm just I just for
00:49:13.440
them exactly as we want this to run exactly so let me
00:49:20.460
go here let's go search so I'm going to close the previous API I
00:49:25.740
had I'm going to go search earlier today Daryl told me it would be cool if we're doing kind of a blog posts demo on the
00:49:33.240
lists I want to list all the blog posts that are in my blog and it appears that Daryl is
00:49:40.680
is very fluent in Latin in in good Lord so we're gonna do we're gonna do that so
00:49:47.099
basically we have an API somewhere I'm going to search for it I'm going to do blog
00:49:53.099
so let's find two I should find two yeah there you go so there's the Blogger API
00:50:00.060
who uses you use it oh my God move remove do
00:50:07.079
something there's cool stuff like you're an xjs like static web app or whatever but anyway
00:50:13.740
um and then there's a second one and it's posted on my personal app that's what I did here I provided my own
00:50:20.579
API to this API that lives somewhere in the cloud so I'm gonna I'm gonna select
00:50:25.859
it it's the second one I'm gonna go here and it's gonna load it right here and there's two sexy Imports
00:50:33.000
why would you suppose in the second one which is use it right but Daryl this morning told me I really
00:50:39.960
just want to see the posts so fair enough I'm gonna go and I'm gonna see the cups I'm gonna go here and I really
00:50:47.220
care about um performance so I don't want to have music I don't want to generate too much
00:50:52.260
code for nothing I just want to focus on post I'm gonna go here I'm going to
00:50:57.420
call it the blog um I'm gonna call it uh it needs oh damn
00:51:04.099
wait I can view that oh it's worse every day I'm surprised
00:51:11.579
but um and now we're gonna put again some Ruby generation I'm gonna think of it have you seen that it literally takes
00:51:18.300
a second like we do that and boom We generate it um I'm gonna go here and then we have the
00:51:24.300
blog which has exactly the same structure that we had earlier there's a client that calls dot post and then pose
00:51:30.720
there's a DOT get and then everybody's happy and this is where things could go south
00:51:37.619
because I'm going to do life coding in a language that uh I actually think I
00:51:43.859
appreciate in in the structure and the way it's built I'm just not very proficient like I love how German sounds
00:51:51.359
but I'm not proficient in German so pretty much the same thing um so the first thing is I already have
00:51:59.700
um a gem file which are are different packages gems got to be that
00:52:05.760
we publish um that we have are abstractions our Json serializer because that's a Json
00:52:11.339
API that we're calling it and our HTTP client that will handle all of the HP
00:52:16.500
connection and do all the call we're using further um in in this case sterilization finally you notified how
00:52:23.400
we do it well do it yourself like you just plug into our stuff you can hear it from from our um our abstractions and
00:52:31.500
very very clear on how to to get I require some of them
00:52:38.640
close the file for whatever reason uh just to make sure I'm gonna do I'm going to install my bundle
00:52:45.000
um it's
00:52:55.619
seriously I don't know what's the cost of that thing but oh my God it's welcome to the
00:53:02.460
Future it's it's crazy what you've done so you're gonna see actually why you're gonna see all the compilent stuff
00:53:08.640
happening um so first thing yeah
00:53:17.839
previous model got from GitHub for my club craft yeah exactly but that's the
00:53:23.280
one I'm building I know that it's seven speaking um so first we're gonna need
00:53:30.720
off we're gonna need to authenticate well that API does not require authentication but we really require an
00:53:39.720
off mechanism so we have our own Anonymous uh
00:53:45.839
uh yeah it's on the kitchen provider so we're gonna do uh off provider
00:53:58.500
already created created this here I'm going to do a new
00:54:04.140
do I need the parenthesis there I don't think if it's
00:54:11.760
um that's actually cool because it makes everything some more so much more focused on the video so whatever so then
00:54:17.460
afterwards that off needs to be passed into how I'm gonna talk with HTTP if I
00:54:22.920
need to append to a header an authentication token or whatsoever and to do that if I need to create my own uh
00:54:30.839
request adapter that will adapt my request and we'll kind of play with uh what's coming back and how I want to
00:54:37.260
inject off so I'm going to do a uh request adapter equals
00:54:44.520
um Microsoft Friday and I'm gonna do a Friday request adapter and here I'm gonna pass in my
00:54:52.020
off why not I say every request needs to go through that off so the off
00:54:58.200
know how to do things you don't just use the off provider to do that by the way you deleted the dot knew my
00:55:04.740
mistake then constructs are very definitely right that's why
00:55:12.140
because then you're like damn then afterwards I need to have my client
00:55:18.180
the client that talks to my blog post so I'm gonna go here um I think I need to do that right
00:55:25.339
in that case log slash blog client
00:55:32.280
um in this case or not we'll see uh and here I'm gonna
00:55:39.180
happen far I'm gonna look at the guy that does I expect here and this is this
00:55:44.880
is where copana comes in thank you co-pilot does it for me it's great
00:55:52.079
um so I create a new I passed in my request about this so when you come to this API use every customer we'll talk
00:55:58.380
with this uh Provider by the capital and this is where we really call our API
00:56:04.020
I have a client it's authenticated in our case it's not but it's good that's where you can do client Dot
00:56:12.540
Dot why do I have the I know why
00:56:18.480
because this I think yes and now I can find my posts
00:56:26.640
nothing crazy it's just using Ruby in this one but now I can do
00:56:33.420
that again and then we learn about that fiber thing uh to do Ascension concurrency sound so I'm gonna do a
00:56:39.960
resume I'm not being the exact good way but um
00:56:45.960
and I'm gonna do this uh I don't think that would make sense actually
00:56:52.740
I'm gonna do a post title does that make sense
00:56:58.980
the the thing that does not make sense is I know that my API returns an object
00:57:04.440
has a value prop in the value prop has all the array of posts so I'm just going
00:57:10.079
to go here and add that value and the resume that I can get so
00:57:16.319
I go here the the I do Ruby on
00:57:29.540
that's great think about if that is a Twitter
00:57:34.619
timeline and we can only call it 30 times a minute or we can only call it 30 times an hour
00:57:39.839
how would you handle it how would you like would you kind of keep a counter and you're like
00:57:47.819
how do I handle but Twitter will tell you and by the way you're up to X percentage of your quota come back in
00:57:55.440
five minutes or whatever that's the beauty of using this because all of that retry handling sterilization is not
00:58:02.940
included so if I'm I'm hammering this API my phone will not break it's going to
00:58:09.240
automatically oh I got um at 429 from the API
00:58:14.339
a little bit and then okay now I'm good I'm gonna call I'm gonna hit the response back and I'm gonna show it so all of that is totally abstracted for
00:58:20.700
you you don't need to think about this um you're not happy with our implementation there are specific things
00:58:26.940
that your internal apis does that we don't account for bringing your own middle rail here and
00:58:33.180
we're going to handle it for you so last thing we're 802 or okay before we
00:58:40.619
spend like four more minutes on on vs code I know because like 31 minutes without cooking so
00:58:48.359
uh what we usually spend about an hour and that's working time so yeah so this is this will give us more topics to
00:58:54.780
network about exactly exactly so Daryl in the afternoon he called me was
00:59:01.079
in my car and he was driving downtown to have like his gazillion number of videos
00:59:06.540
this guy is very busy um he called me like I'd love to get the users also
00:59:13.079
oh well my code is generated don't know and let me trap
00:59:20.460
that's really the beauty of it could ask that block file right
00:59:26.940
tells me what are the posts what are the the patterns are included what are the apis are included okay we're here you
00:59:32.880
can go right click and say select lock file from API explore review okay so
00:59:38.220
basically it brings my API and brings it back for me so
00:59:44.880
cool okay I have posts that's great that's being you know the ad user is
00:59:51.119
that all really really wants the user so okay I'm gonna hit play it's remember is
00:59:57.660
everything I already told him what's the name space what's the name of the client and so on so far it generated it and now
01:00:04.260
I can do trying to die users
01:00:13.319
resume dot value each new user
01:00:19.559
and that will work this that's actually a name and now I should have both users
01:00:25.799
and books but imagine starting with a small footprint you you said it earlier I'm gonna try stuff
01:00:32.760
and then you're like oh this you guys you built your own HTTP client and then oh I'm gonna add some more and
01:00:40.079
then somebody joins you in your team and then this becomes out of control or this
01:00:45.480
we're just generating a new a new endpoint on that API so that's
01:00:50.640
what killed it is providing you as a Dev the power to connect to
01:00:56.760
I'd love to say to any API or any HTTP API we have to be more honest by saying
01:01:02.220
any open API described HTTP API but with a decent opening when it is in the open
01:01:08.400
API but our goal is to really shift the momentum instead of you doing
01:01:15.359
okay I need to connect that plug thingy let's go uh Google or Bing
01:01:22.700
will be uh or or ask check GPT to do it for you and it's going to give you
01:01:29.099
zillions of options or Google will give you gazillions of options and you're like which one do I take or do I take
01:01:35.760
the official one and I get bloated and that's really where you are in control now of any type of connections you're
01:01:43.740
making through API yep questions
01:01:48.839
um I'm thinking something but yeah like you are using like post or get to resume uh so this is like Bill in every module
01:01:57.599
like same or it's different what do you mean like there is a method like post or get it resume like resume means like
01:02:04.559
this is a method to continuously get the data so the resume is part so we we made
01:02:10.079
a large picture Choice as part of our Ruby implementation to use fibers that helps you do concurrent calls and
01:02:16.200
basically doing asynchronous calls so that's how you you basically
01:02:22.680
um asks okay you ask okay now Ruby do the actual call now instead of just like
01:02:28.680
hearing it now it's it's resuming it so the return the value you're getting back is is the actual collection or the model
01:02:36.960
or whatever from the API from the doctors but the rest is all what we project like the users is think about
01:02:45.660
twitter.com slash two yeah slash get slash
01:02:53.000
yeah and then you would get a Json object with a value product
01:02:58.880
dot path segment.pathsegment.class segment. however many past segments in your url
01:03:04.940
dot HTTP method yeah and that's how you get the results if you want to do a post you're going to
01:03:10.740
just post um like an anonymous object in there you're going to post your ID and your
01:03:17.280
user you want to add or you want to do a delete you're going to pass in just the ID of of of of the user or or whatsoever
01:03:24.900
and we handle all of them via really the the core HTTP verbs that HTTP
01:03:31.680
is meant to be used for how many apis are you using posts or
01:03:36.780
billions I've seen that the million refer to
01:03:43.500
referred to good and B to be the nicest if you get duck also learns yeah how how
01:03:50.640
much would you pay for this oh and you know if it keeps you in vs gold
01:03:56.059
okay so so how much how much because you'll be on top of the world
01:04:02.880
exactly everything exactly so AP so open API as a concept of embedding for
01:04:09.660
operation can you go and search for craft please
01:04:16.200
no I'm gonna search for GitHub can you search for GitHub please yes I'm interested yes I'm usual yeah
01:04:30.960
a bigger or maybe I should pick a little bit more this is the tree I want to see the Emojis one because I'm
01:04:37.619
a big you like the Emojis mom yeah where's the Emojis I don't know where it is let me just see if I can find it
01:04:43.500
oh that's good well there it is there's a filtering capability that's great wait interesting this version which is still
01:04:50.460
in the pr in our repo all right makes the tree a little bit bigger not only does it have the path segments in the
01:04:56.339
tree it now tells you what the operations are so you can now project out not just I want this re this path
01:05:03.180
but I only want the put or I only want the get or I won't so you can control it
01:05:08.880
down to the method and we get this delightful little icon here which when I
01:05:15.540
click on it it's going to go oh you want the docs oh yeah emojis on GitHub yeah it's right there
01:05:22.500
you want to know what the response looks like it's right there okay that's cool
01:05:29.520
and as uh it's called hyperlink
01:05:35.940
the web was built from yeah yeah as Sebastian was saying here we can do Microsoft graph
01:05:42.119
and we can pull this down and it's bigger so it'll take a little bit longer
01:05:48.420
at the moment we have plans for making this faster so I don't have to fill in the time as much with a little bit of
01:05:54.660
dialogue whilst it's loading Adventure but we also have an open issue
01:06:00.000
for could we have the Legacy uh so there we have this is just the V1
01:06:06.119
API the V the beta API is even bigger
01:06:11.339
um and the same thing here I can search for applications I have to spell applications
01:06:20.220
and then I can go here and it takes us into the Microsoft graph documentation for that particular endpoint as well oh
01:06:33.180
previous example Aaron however we can help you you can
01:06:41.160
retrial yeah can you get me the list of attendees of a meeting
01:06:47.280
enough um let's search for attendees uh well
01:06:53.700
they're not called attendees well there's an attempting reports after
01:07:01.619
the fact report no
01:07:07.500
we're gonna have to go through online meetings yeah online meetings we are under a user so
01:07:13.980
oh yeah so basically you can't even get I schedule the meaning the meeting is mine so you could slash user slash
01:07:21.619
ID whatever slash online meetings and I'm going to be able to see all my meanings you're going to select that ID
01:07:27.900
slash identity report the get and you're good to go so you have to know
01:07:35.059
the the organizer of the meeting beforehand well that's why I think that
01:07:41.460
the easiest one is the other endpoint which is more agnostic uh which is like
01:07:47.220
Communication online meetings and you don't think the I the ID of the meetings almost impossible okay
01:07:53.880
yeah you need to be a bot to basically get on that so part of my job is sitting
01:07:59.520
through API reviews from teams that bring these apis to Microsoft graph and if I had a dollar for every time we've
01:08:06.299
had an argument with this team that you have to make it easier to get that online meeting ID but there's reasons
01:08:11.940
why they can't but yes that's would be really really helpful
01:08:18.000
okay basically any and that's the duty right when you know the domain of the API you're looking for filtering is
01:08:25.199
super powerful because like literally it's 2700 documentation page that we
01:08:31.679
have for our API if you know the join URL you can filter on the collection using the join URL as
01:08:39.660
a filter like it makes my screen skin cool just even admitting that yeah
01:08:47.279
there you go did you close my deck no it's my VM okay I have like I have a
01:08:54.660
roadmap slide just to kind of talk about where we're going just to cap off the story
01:09:03.179
do that it's yours oh enjoy
01:09:08.940
road map so
01:09:14.880
we've got the ca that we'll see Sharp GA or made generally available as Microsoft
01:09:20.759
Lincoln we got to get all the other languages too you saw a bunch of them were like experimental preview we need to get
01:09:27.359
those all to stable so that we get broad support um one thing you might not notice is we
01:09:33.299
actually have a generating of a CLI so if you have an API and you want to generate command line tool we can
01:09:39.239
generate a CLI for it uh to be able to just call it from the bottom line um for those in the Microsoft world will
01:09:46.259
probably in the future you're going to do the Powershell too um you've already seen our IDE integration we've talked about our
01:09:52.620
building Partnerships with red hat and GitHub documentation is or if it's it's very
01:09:58.620
soon as soon as our Dev comes back from from bit getting married we'll get that merged in and also documentation from
01:10:05.580
another stand for standpoint where the tool is the owner has a documentation portal where you can
01:10:10.800
learn about how to install how to use how to configure how to bring your own implementations on our own abstractions
01:10:17.640
and so on if I actually hit oh if I've actually put the learned it's on
01:10:23.040
our main Microsoft Port archa of the documentation no
01:10:28.260
no the backyard highways and you're especially typing on your own yeah and it's plugged into the other one that's
01:10:34.080
probably why it's not working um yeah as Ruby is experimental we need to
01:10:41.159
do work we need to find a Dev who's got some skills to help us out there
01:10:46.500
um and dedicate some time to actually bringing the last pieces because like we
01:10:51.540
were doing this yesterday going try this again okay we have to go build our own API
01:10:58.380
because this is a bunch of edge cases because there's lots of things that can do so so there was some smoking mirrors there
01:11:05.040
okay yeah yes I know it's a networking yeah it's very similar to how we project a
01:11:11.100
code if you want to try it out I'd love to get an issue in the repo AKA like Ms slash Toyota
01:11:17.219
and you're gonna land on the GitHub repo an issue and say this doesn't work this
01:11:22.500
doesn't work this should be like this here's the proposal I'd love to hear it yes out of curiosity out of the trials
01:11:29.640
in there that you made uh what's the rough percentage of working out of the box Ruby apis and I
01:11:37.320
know it's a work in progress in the end any better than just spending these Vacations so here's the scenario um where we have issues is
01:11:46.199
we build Kyoto as a generic tool but our test bench is
01:11:52.320
Microsoft graph Microsoft graph has some special cases and I would say that
01:11:58.500
I wouldn't say the most special case but is we never return a collection
01:12:03.780
we returned an object value that has a collection so apis are
01:12:10.920
ascending raw arrays arrays you just don't work right now holy moly yeah it's
01:12:17.460
a very hard exactly so so basically the the code it's literally there's a single
01:12:24.300
line of code it needs to change to support that scenario too treat it as a collection
01:12:30.360
like from the from the get-go and not just as I guess one problem so that's
01:12:35.400
the old we could have worked way easier in that that use case was in there and we did
01:12:43.260
not catch it because we highly got far enough in our in our testings all of our
01:12:48.960
other languages are using like 20 or 30 different open apis from
01:12:55.380
tons of different we're probably 80 there and 90 of apis won't work for one
01:13:01.320
or two reasons yeah exactly so it's a it's a bunch of edge cases that that are
01:13:06.900
more than just edge cases it's not a ton of work yes I have a suggestion you mentioned
01:13:13.500
the CLI I actually own uh
01:13:20.580
uh desktop two weeks I wonder and I've been thinking about the idea of actually Auto generating buoys from uh of web
01:13:29.280
HTTP apis request apis uh so I just want to make sure that suggestion is another idea right so like
01:13:36.840
crafting rest apis in a few weeks let's talk about this mod element here so I
01:13:43.500
talked about the fact that we don't use templates we have a code dog we have a code Dom that's optimized for generating
01:13:49.520
glimmer by the way okay um and
01:13:56.460
while that is that's our bread and butter that's what we are code generating there are a bunch of other
01:14:02.159
things that you might want to generate unit tests you might want to generate sample code you might want to generate
01:14:09.060
UI things and or you might want to generate server code like scaffold up
01:14:14.880
from an open API description a an API a rails service
01:14:22.080
um and so what we're going to do is take that code down that we generate out of
01:14:29.100
our open API description and just project it out in a standardized Json model so then you can
01:14:36.120
take that and feed it into some kind of telling the thing language so you will know what our client Library looks like
01:14:42.600
and so you could generate tests uh you could generate sample code you could
01:14:48.179
generate UI that then can call those endpoints because you will know what the shape of our client libraries are going
01:14:54.300
to be but you get a machine readable machine processable format in order to
01:14:59.580
do other kinds of code generation so that's one of the things that's on our list to do soon
01:15:06.480
um we we can't have a slide at the moment without saying we're doing something about llm prompt management
01:15:13.100
AI otherwise otherwise our management think we're just not doing our jobs so it had to go on there
01:15:19.440
um so what is it you're actually doing in that space well it's or you're just putting this
01:15:26.340
um so snipper generation is an interesting one right do you really
01:15:33.380
need code to be able to generate a code snippet to be able to call an endpoint
01:15:39.440
or can you just construct a prompt that says this is kind of how kyode API
01:15:46.739
client code looks like and this is how you set headers and this is how you do parameters and this is how
01:15:53.340
a path translates into a call here's a bunch of examples of the problem now I
01:15:58.860
want to go and do this job right I want to do this other thing can you just go generate me the code and
01:16:05.400
I talked earlier about this the idea of the service adapter uh back in oh I'm
01:16:11.520
going the wrong way okay um in the little architecture diagram I
01:16:17.760
had no idea what that slide is why it's indestackable
01:16:23.219
I think it's in the hidden one we maybe do remember yesterday so this
01:16:29.400
this service adapter here yeah um this is handwritten code that provides
01:16:36.600
you with a friendly interface to our standard stuff when you sit there and start typing that
01:16:42.719
co-pilot that does awful work for you it figures out once you've got a few examples in there of how you want to
01:16:48.600
call our API client code it's really good at that we could go a little bit
01:16:53.880
further and build some tooling into our vs code extension so you could start asking as natural language questions and
01:17:00.659
we can just figure out by constructing a prompt that says this is how you call kyota so that's that's the kind of thing
01:17:06.840
that we are going to be experimenting with uh with regards to prop generation how to easily create these kind of
01:17:15.000
adapter methods call our apis why would you focus on the adapter and not on the code generator itself
01:17:23.000
itself was was prettier and more and easier and more language uh Focus to
01:17:30.920
predictability is right now a big issue for these things you are going to ask
01:17:36.600
the same question twice you're gonna get two different responses um so we we I think if we train the
01:17:44.280
model enough it's it could potentially like basically hey
01:17:50.520
here's an open API the user wants to call this this this this endpoint generate me and then well that's exactly
01:17:57.480
what the chat GPT plugin is doing today if in the chat GPT plugin you point it to an open API it puts the open API
01:18:04.679
description on the prompt and they have one they have a generator that generates python code that then calls that API and
01:18:11.340
figures that it's all done runtime on the Fly and so the plugins and checks of the T are actually using AI to
01:18:17.640
understand how to use the plugin like there's no like instructions it's all AI
01:18:23.219
bas3 we are exploring there's of course everybody's trying to figure out what to
01:18:28.500
do with it where it can really but there's so much learning to do in that space and it's changing so fast too
01:18:35.400
um we have built a web experience you can actually go to kyoto.dev and actually do all of this generation on
01:18:42.900
the web app uh it's actually because it's all written in C sharp it actually load downloads a Blazer app uh which is
01:18:50.520
comparison it's a webassembly effectively um we also think there's an opportunity
01:18:56.460
for improving API search using llms uh I want to be able to find API that does
01:19:02.420
tells me how to what is the attendance of an online meeting
01:19:07.560
There's an opportunity there for better semantic search indexes that can
01:19:13.320
understand the question that you're asking and find you the apis that can actually do the things that you're
01:19:18.960
interested in rather than just doing keyword searches that we're doing at the moment there's also a really interesting story
01:19:25.800
around workflow which is we build clients that call one API endpoint for
01:19:32.340
99 of cases um wouldn't it be nice if we could figure
01:19:38.219
out how to generate code that knows how to achieve a goal by calling this endpoint and taking the result from that
01:19:45.239
endpoint and then generating the next one or calling the next one and taking the output of one to be able to call the
01:19:51.780
other in open API there's a concept called links which start down the path
01:19:57.120
of being able to connect operations together and say how they're related we are identifying the number of gaps in
01:20:03.480
the open API specification for certain scenarios it's not easy to draw describe
01:20:08.760
next page links if you want to build a page through questions there's no easy
01:20:14.159
way to describe um how when you go and create something
01:20:19.440
you get a location header that tells you where to go and get the thing that you just created and that's another thing
01:20:25.800
that we want to start figuring out how to get into the open API description we have concept of long-running operations
01:20:31.320
which is I went to go do something it gives me a 202 to say yes I'm doing it
01:20:36.780
but it's going to take a while here's a location header for a status monitor that you can pull to find out when it's
01:20:42.600
done wouldn't it be nice if we could actually coach in for those scenarios also yes
01:20:48.300
this reminds me a bit of something uh built in the past by Yahoo it was called
01:20:53.460
Yahoo stinks I think the pipes or pipes sorry would you allow me to create a
01:20:58.500
link multiple feeds of for example atom feeds and then build a new list out of
01:21:05.520
multiple block feeds for example that's kind of similar it's not right yeah yeah there's all kinds there was focus on on
01:21:13.020
HTTP API I wish I could remember there was a there was a guy from South America in the Ruby community that did some
01:21:19.800
awesome work in the hypereal space back in the early 200s too there's all sorts
01:21:25.320
of stuff there's been there's lots of opportunity for us to be able to connect these different operations together and
01:21:31.560
actually between a combination of rich or open API descriptions and more AI
01:21:37.320
that can do the understanding the natural language of what you're trying to do and be able to break down that
01:21:44.520
natural language request into simpler steps and then mapping it to uh HP
01:21:50.100
requests I think there's a lot of opportunity even here thinking uh cloud with like basically workflows or could
01:21:59.280
could almost become like developer focused zappier like when you
01:22:05.940
do sapiers and when you do uh if this and that like in because that could be an API well that could be across apis
01:22:13.980
but because they all have the same structure you know share the same missing Concepts because they're all
01:22:19.500
generated using the same clients you could have a really really powerful instruction they don't need infrastructure anymore to do those kind
01:22:26.760
of integration scenarios you just need good API descriptions and some clever API to generate the code that will glue
01:22:34.679
the pieces together and we should have killed that last one and hence filtering because we pretty much already done it because we can filter our methods now
01:22:41.040
yeah filter so um yeah these are the things that we are building these are things we're playing
01:22:46.679
with it's open source if you want to come take a look uh in that next slide
01:22:52.800
that's the GitHub repo of Microsoft Toyota um
