Best of GraphQL — June 2024

1. 1
   Article

   Community Picks·2y

   API Design: From Basics to Best Practices

   Learn about API design principles, understand different types of APIs, and discover best practices for creating efficient, secure, and easy-to-use interfaces.

   114

   2
2. 2
   Video

   ThePrimeTime·2y

   I Am Done With Graph QL After 6 Years

   The author shares their frustration with GraphQL, pointing out various security and performance issues. They recommend using an OpenAPI 3.0 compliant JSON REST API as an alternative, highlighting the benefits of type-safe schemas and code generation. The author also discusses the drawbacks of using GraphQL and the complexities that arise.

   19
3. 3
   Article

   Community Picks·2y

   Writing a GraphQL Backend by Hand is Long Gone

   Building a GraphQL backend by hand comes with challenges such as complexity, performance bottlenecks, security vulnerabilities, and reliability issues. GraphQL is more like SQL than REST or gRPC. The future of GraphQL is moving towards generalized automated solutions and standardization.

   18
4. 4
   Video

   Theo - t3․gg·2y

   Six Years Later, I’m Over GraphQL

   GraphQL has its benefits, but there are major concerns regarding security, rate limiting, and performance. REST APIs may be a better choice for certain situations.

   16

   2
5. 5
   Article

   Community Picks·2y

   Showing Blog Articles in Blazor with GraphQL

   Learn how to display blog articles from a Hashnode headless blog in a Blazor site using GraphQL. The process involves setting up your Blazor project, activating Hashnode's headless feature, installing the necessary GraphQL client libraries, creating proper models and services, and setting up dependency injection. Finally, a Blazor component is created to display the articles formatted using Bootstrap CSS.

   13

   1
6. 6
   Article

   Javarevisited·2y

   Implementing Robust GraphQL Authentication with Apollo: Leveraging Custom Directives and Plugins for Precise Access Control

   GraphQL's single endpoint architecture necessitates a unified access control strategy, unlike REST APIs. Traditional methods of endpoint-specific authentication don't apply. One solution is using custom directives and Apollo plugins to implement fine-grained access control efficiently. These plugins allow centralized authentication mechanisms, support OAuth 2.0 integrations, and offer features like encryption and redaction of sensitive fields. The new authorization plugin provides a reusable framework that simplifies maintaining consistent access policies.

   11
7. 7
   Article

   Lobsters·2y

   Why, after 8 years, I still like GraphQL sometimes in the right context

   The post discusses the concerns and trade-offs of using GraphQL, including security, performance, maintainability, and authorization. It suggests persisting queries and not building public GraphQL APIs unless one is familiar with the challenges.

   10