Coding Blocks avatar

Dexa/Coding Blocks

Learn more
Published Sep 17, 2019

3factor app - Realtime GraphQL

Dive into the world of GraphQL with Joe Zack and co-hosts as they dissect its capabilities in schema language, real-time data handling, and integration into modern tech stacks, contrasting it with traditional REST APIs to unravel its transformative impact on application development.
Episode Highlights
Coding Blocks logo

Topics covered

Popular Clips

Episode Highlights

  • Versioning

    GraphQL's approach to versioning is a point of contention among developers. highlights that GraphQL lacks built-in versioning, which is often seen as a disadvantage compared to REST's straightforward versioning through URLs 1. However, notes that GraphQL allows for the deprecation and addition of fields without breaking existing queries, which can simplify API evolution 2. This approach, while innovative, raises questions about the complexity of supporting multiple API versions.

    Maybe they're thinking is like, well, do you really need to support multiple versions of your API? Like, maybe that's just being overly complex.

    ---

    Despite these criticisms, some argue that maintaining multiple API versions may unnecessarily complicate development.

       

    Data Handling

    GraphQL's data handling capabilities offer significant advantages over REST, particularly in preventing over-fetching and under-fetching. explains that GraphQL's ability to specify exactly what data is needed can enhance performance, although it requires careful implementation to avoid inefficiencies 3. praises GraphQL's tooling, such as GraphiQL, for its robust capabilities, which streamline development and data management 4.

    The tooling on GraphQL is amazing. Graphical especially. That particular tool is killer.

    ---

    These features make GraphQL a compelling choice for developers seeking efficient data retrieval and management.

       

    Security

    Security concerns are a significant consideration when using GraphQL, as points out the potential risks of exposing sensitive data through poorly managed queries 5. emphasizes the importance of following best practices, such as separating authorization logic from schema definitions, to mitigate these risks 5. Despite these challenges, GraphQL's open specification and permissive licensing offer flexibility and transparency, which argues can build trust among developers 6.

    GraphQL is a specification. It is not an NPM package that you add to your code. It's not some bits that you download.

    ---

    This open nature allows developers to customize and secure their implementations effectively.

Related Episodes