Different states will focus on different metrics; imagine a network state premised on improving its citizens’ overall life expectancy, or one aimed at provably right-shifting the income distribution for all. You get what you measure.

Rejecting based on query complexity (cost analysis)Amount limitingDepth limiting

We can reduce the load on the database significantly by batching and caching with Data Loader

The issue is that potential attackers can easily call complex queries, which may be extremely expensive for your server and network.

If you are in a development environment, it is definitely useful to allow introspection for various purposes. In production, however, it can leak important information for potential attackers, or it can also just reveal information about a new feature which has not yet been implemented on the frontend.

When testing and trying out your mutations, I suggest you only use variables, and use inline arguments as little as possible. This will force you to make GraphQL documents that can be copy-pasted right from the GraphiQL into your integration test suits and to your frontend. If you only use inline arguments, you will need to rewrite the GraphQL document in the client.

In most cases, it is much better to use the object type and input object type. If you want to add some field as the return, you should not use simple scalars as return values, as this will cause your GraphQL document to break.

GraphQL does not support versioning out of the box, but is designed in a way that minimises the need for it

The risk is that when you build a new thing for the second time, you'll feel less cautious and more experienced, and end up over designing the whole thing.

Avoid implementing things that you might need in the future in favor of things that you definitely need today.

When building queries, focus on the underlying data, rather than how it's represented in your application.

Describe the data, not the view. Make sure that your API isn't linked too closely with the demands of your initial interface.

Your objective with GraphQL should be to create a unified, cohesive graph that allows users of your API to create subsets of that graph in order to build new product experiences.

GraphQL minimizes the amount of data that needs to be transferred over the network

If you are building a more complex app, just do not use GraphQL schema generators blindly.

it is much better to nest the output types. This way we can call everything with one single request, and also perform caching and batching with the data loader.

Whenever you fetch lists, I suggest you use paginated if it makes sense. You will avoid breaking changes of the schema in the future, and it is almost always a much more scalable solution.

Returning affected objects as a result of mutations

Using the input object type for mutations

Use consistent naming in your schema

Marc Andreessen actually has a seat on Coinbase’s Board of Directors

MAGA

Indeed, there have been 57 hyperinflations in the world that we know about. However, they all took place amid political and social chaos;

Are banks that untrustworthy?

many people accept the scientific consensus on, say, vaccine effectiveness not because they value peer-reviewed research but because they are impressed by people in lab coats who use big words

the fact that many Bitcoin enthusiasts say bizarre things does not, in itself, mean that cryptocurrencies are a bad idea