Tell me, why was your technology created? We don't need a whole history. ![]() At some point in the past, they did not exist. We're now at a point where with any of the three technologies you represent, someone can come in and just implement that technology right now. For various reasons, this has led to the invention of countless protocols, patterns, and paradigms for developing APIs. APIs have existed for as long as we've needed two systems to be able to talk to each other. I want to start off with brief origin stories. He's not behind a microphone here at QCon, he's behind a microphone as co-host of the 'APIs Unplugged' podcast. Matt McLarty is a Global Field CTO for MuleSoft, co-author of two O'Reilly books on microservice APIs architecture. Twitter picked her up after she did an amazing job implementing GraphQL at Condé Nast, where surprisingly, they did not put the GQ in GraphQL. Michelle Garrett is part of the team building Twitter's large scale GraphQL API. Alex is currently an engineer at Netflix, and was previously at Google, who gave us the g in gRPC. It's just a helpful way to create a discussion with diverse opinions, because we really want to understand, what are the tradeoffs you need to consider when evaluating your options? Background ![]() I don't want to paint any of the panelists into a corner as only an expert on one topic. Any good architect knows the only time you should ever use always or never is to say we will never do an absolute. I'm joined by three panelists, each chose to be a representative of one particular API technology, more or less.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |