The post outlines the initiation of a new project for a multi-tenant music collector’s database. The objectives include personal use and sharing with others, along with the selection of tech stacks. The project aims to provide a personalized, secure, and collaborative platform for enthusiasts to manage and appreciate their vinyl collections efficiently. Key decisions include... Continue reading →

While GraphQL provides a flexible and powerful approach to building APIs, there are some common anti-patterns that developers may unintentionally implement when working with GraphQL query resolvers. These anti-patterns – the opposite of yesterday’s top 10 practices – can lead to issues such as performance bottlenecks, security vulnerabilities, or maintenance difficulties. Here are some of... Continue reading →

Here are 10 best practices for GraphQL accrued from dozens of GraphQL API implementations: Remember that these practices may vary depending on the specific requirements and context of your GraphQL implementation. It’s always recommended to stay updated with the latest best practices and community guidelines. Continue reading →

When building a GraphQL API with nested queries and relationships – specifically in a relational database – it’s important to follow best practices to attain efficient and performant data retrieval while preventing overly nested queries Continue reading →

When planning a GraphQl Schema design, choosing appropriate type names and casing conventions is essential for creating a clear and consistent API. With no industry-wide standard, there are some common practices and recommendations that I tend to follow when setting up new schema and related project assets: Continue reading →