• Response keys deduplication
• Response sanitization (?)

There must be a request throttling mechanism built-in in order to prevent DDoS attacks.

Implement a great suggestion from here.

What

Need to add scalable logging system to the server.

Why

To write the request/response logs, including errors for better monitoring and debugging.

How

1. Introduce a logging abstraction above controllers.
2. Make a configurable pool of dynamic log files, depending on their file size.
3. Write incoming requests and responses to the logs.
4. Write meaningful errors to the logs.

What

Add normalizr to normalize incoming responses.

What

I suggest to adopt a RESTController from Apollo.

Why

The mentioned controlled is a substitution for the current custom Controller class. It should also provide caching and optimization built-in.

Fixes #2

How

https://www.apollographql.com/docs/apollo-server/features/data-sources.html

Hi! While it may be fine for this use case, I suggest using Prototype chain inheritance over Class inheritance

https://medium.com/javascript-scene/master-the-javascript-interview-what-s-the-difference-between-class-prototypal-inheritance-e4cd0a7562e9

What

I propose to define a clear resolver/controlled contract.

Why

At the moment different resolvers ping different controllers differently. I want to have a unified interface of controllers calls to make a more intuitive usage of both.

What

Need to export the main functionality like an Express middleware.

Why

So there would be two options: standalone server, and a middleware establishing the same functionality on the given route of the existing server.

What

I suggest to add a request query to the server setup.

Why

Request query allows to accumulate and resolve high load of requests on the server. It also improves server's scalability.

• GraphQL Documentation - Pagination

• Need to consider cookies as of client-server agreement to transfer sensitive data for authenticated users.