Server architecture for large schemas. Type extensions?

Bắt đầu bằng cách xem xét bố cục được mô tả của User.fs, Organization.fs và Query.fs cùng với đặc tả GraphQL Object Extensions được liên kết trong issue. Xác định xem thư viện đã có điểm truy cập cho schema hoặc định nghĩa object phục vụ kiến trúc này hay chưa. Công việc được xem là hoàn tất khi có một khuyến nghị đã được thống nhất hoặc một kế hoạch triển khai được xác định phạm vi rõ ràng cho các trường quan hệ xuyên tệp và các phần mở rộng.

My team is migrating an existing GraphQL API from JS to F#. Our API has a lot of types, so we decided to create a file per type (Define.Object).

The file structure looks like this:

• Schema
  • User.fs
  • Organization.fs
  • ...
  • Query.fs

If Organization has a users field that returns ListOf User, you can simply compile User.fs before Organization.fs.
However, this doesn't work if User also needs to have an organizations field, because F# doesn't allow mutual recursion across files.

What is the recommended way to architecture a big server like this? The samples use a single schema file, but unfortunately, that's just not feasible for our use case. If we did this, we would eventually have a file with 20K+ lines of code (judging by the size of our JS API).

A solution might be supporting Type Extensions. Especially, Object Extensions: http://spec.graphql.org/June2018/#sec-Object-Extensions

With Object Extensions, we would be able to define these relationship fields at the return type module instead. In my example, Organization.fs would add the organizations field to the User type, and User.fs would add the users field to the Organization type.

This architecture would work out pretty nicely for us because the querying and authorization logic needed to return records of a type would remain in its module as opposed to being spread across the codebase.

Supporting GraphQL extensions would also allow users of this library to build GraphQL microservices, that could be composed using tools like Apollo Federation.

If you think that's a good idea, I'd be more than happy to contribute. Thanks!