Explore >> Select a destination
|
You are here 
|
www.stackchief.com | ||
| | | | |
blog.hao.dev
|
|
| | | | | Building a GraphQL API requires a deep understanding of the technology and best practices. It offers developers a high level of control and freedom, which is why it is so easy to get started. However, it is also why people can design themselves into a corner if they are not careful. Security and performance implications are just typical issues of software development. GraphQL also requires that the schema is well-designed and easy to maintain; otherwise, the development team will run into a world of pain. Additionally, the development team must be trained and skilled in using GraphQL, as it requires a different way of thinking about data and APIs. In this article, let's discuss when it is a good choice to adopt GraphQL and who it is for. | |
| | | | |
hackteam.io
|
|
| | | | | There have been many discussions on Twitter around "GraphQL versus tRPC" for building a modern backend for your application. As a developer working with GraphQL in the past years, this triggered me to compare the two and see what they are both excellent at (and what they are not). | |
| | | | |
coady.github.io
|
|
| | | | | [AI summary] The article argues that GraphQL, while solving over-fetching on the client, recreates ORM inefficiencies on the server and advocates for introspecting query selections to build efficient resolvers. | |
| | | | |
bartlomiejmika.com
|
|
| | | How do you write a Golang server using gRPC from scratch? Heres how to do it. | ||
