Phil Haack - GitHub

Download this episode

Download Video

Download captions

Download Captions

Description

Phil Haack is our guest this week. He works for GitHub. Before that, he started ASP.NET MVC and NuGet at Microsoft.

Phil on Twitter: https://twitter.com/haacked

Phil's blog: http://haacked.com/

The gang of foreheads book: http://www.barnesandnoble.com/w/professional-aspnet-mvc-10-rob-conery/1100173351?ean=9780470384619&st=PLA&sid=BNB_DRS_Core+Shopping+Books_00000000

Tags:

.NET, GitHub

Embed

Format

Available formats for this video:

Actual format may change based on video formats available and browser capability.

    The Discussion

    • User profile image
      E

      Phil knows his stuff!  Used to enjoy his news/blogs about stuff he was working on for MS.

    • User profile image
      vgotra

      One of the great and bright engineers and persons )

    • User profile image
      MKlymyuk

      This guy looks like Elon Musk

    • User profile image
      Liero

      what Phill described as shaping data in GraphQL, e.g "I want top ten issues and all their comments, but only these field in those comments", that can done in OData for example:

      api/issues?$top=10$expand=comments($select=commentId,title)

      I don't need n+1 calls as he claimed. Am I missing something?

    • User profile image
      Haacked

      Liero, the "N+1" comment was comparing GitHub's GraphQL API to the current GitHub API.

      GraphQL and OData both provide means of avoiding N+1 queries.

      One difference with GraphQL and OData is the query you send with GraphQL is formed as JSON in the request body rather than the OData format in the URL and defines the shape of the data you want back which is also returned as JSON. This is conceptually easier to manage for some.

      But for these kind of querying scenarios, I believe both technologies to be pretty similar.

    Add Your 2 Cents