Thank you for your input. Good & insightful questions. >> instead was a one-to-many relationship between 2 first class entities? This can be treated as virtu

Thank you for your input. Good & insightful questions. >> instead was a one-to-many relationship between 2 first class entities? This can be treated as virtual relationship between 2 entities and can be linked together in our models. This has to be done manually for now. May be we can do better with our UI tool. I've raised an issue to track this - https://github.com/xgenecloud/xgenecloud/issues/6 https://github.com/xgenecloud/xgenecloud/issues/6 one-to-one relationship returns a list instead of an object as of now. >> How does it handle join-tables which implement many-to-many relationships? Does it generate the REST end point for the join-table instead? In GraphQL : the schema is like a graph traversal so a join query is possible. In REST : no - this will have to be created manually. >> How does it handle different subcollection semantics? Subcollections can be handled individually i.e in their own routes or in nested routes in REST framework. CUD operations for subcollections in GraphQL i.e nested CUD operations (mutations) are not possible. >> SQL Query optimisation: N+1 query optimisations are done with data loaders. Please let us know of any other questions.