Tag
Introduction Over the past year at Hashnode, we have been continuously developing GraphQL APIs to enable users to interact with their data and perform various operations. We utilize Stellate as the GQL CDN and take advantage of its Edge Caching capab...
Hey everyone, this article discusses how we manage breaking changes in Hashnode's GQL Public API. We recently announced Public APIs 2.0 and have been rapidly iterating. As a result, we are incorporating feedback and enhancing the APIs. We are thrille...
Building APIs – especially public-facing ones – is hard. There are a lot of decisions to be made, starting with the API concept (GraphQL, REST, etc.) to be used, infrastructure, and much more. But having this is just the foundation of your API, and y...
Once you have created your first schema and your GraphQL server is up and running, it makes sense to implement precautions to prevent it from being compromised by bad actors. In the context of Hashnode, our GraphQL API serves our website and blogs. T...
Rate Limits are a vital part of every API. Especially, since we operate quite a lot of public and unprotected APIs we need to rate limit them. Implementing Rate limits based on IP addresses is fairly easy, especially with Amazon API Gateway and Amazo...
GraphQL handles error codes a bit differently compared to REST Apis. While we still get HTTP response codes like 200 OK 400 Bad Request 500 Server Error It often happens that an error happened even if we received a 200 status code. This blog pos...
The following is a republishing of a summary of a research I was tasked to do in Hashnode. The perspective here is me talking to my colleagues. I chose to keep that perspective to preserve the raw quality this writeup have. So keep that in mind when ...