According to Apollo GraphQL
GraphQL schemas are at their best when they are designed around the needs of client
applications. When a team is building their first GraphQL schema, they might be tempted to create
literal mappings on top of existing database collections or tables using CRUD-like root fields. While
this literal database-to-schema mapping may be a fast way to get up and running, we strongly
suggest avoiding it and instead building the schema based on how the GraphQL API will be used
by the front-end.
But in case of neo4j-graphql-js we have to have the same type and attribute names same as it's in database right?