Volodymyr Pavlenko

With GraphQL having a type system, we see a lot of tools appearing these days that try to generate GraphQL types from databases, ActiveRecord models, or a REST API. While this is tempting to use, and definitely useful at times, by copying our data model or an existing API, we forget to that GraphQL lets us really shape the interface we want to our domain. Try to use that power instead of shaping your API using your data’s shape as inspiration (Avoid Anemic GraphQL).

Therefore, I recommend starting simple and use one port in the beginning, and split it only when necessary.

Here’s a catch: More ports means more code. More abstraction. More wirings. More complexity. The code becomes more spread apart. It requires more mental capacity to understand.