{"action":"created","issue":{"url":"https://api.github.com/repos/graphql/graphql-js/issues/223","repository_url":"https://api.github.com/repos/graphql/graphql-js","labels_url":"https://api.github.com/repos/graphql/graphql-js/issues/223/labels{/name}","comments_url":"https://api.github.com/repos/graphql/graphql-js/issues/223/comments","events_url":"https://api.github.com/repos/graphql/graphql-js/issues/223/events","html_url":"https://github.com/graphql/graphql-js/issues/223","id":115770007,"number":223,"title":"Merging schemas","user":{"login":"xpepermint","id":174279,"avatar_url":"https://avatars2.githubusercontent.com/u/174279?v=4","gravatar_id":"","url":"https://api.github.com/users/xpepermint","html_url":"https://github.com/xpepermint","followers_url":"https://api.github.com/users/xpepermint/followers","following_url":"https://api.github.com/users/xpepermint/following{/other_user}","gists_url":"https://api.github.com/users/xpepermint/gists{/gist_id}","starred_url":"https://api.github.com/users/xpepermint/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/xpepermint/subscriptions","organizations_url":"https://api.github.com/users/xpepermint/orgs","repos_url":"https://api.github.com/users/xpepermint/repos","events_url":"https://api.github.com/users/xpepermint/events{/privacy}","received_events_url":"https://api.github.com/users/xpepermint/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":26,"created_at":"2015-11-08T23:43:14Z","updated_at":"2017-11-29T23:28:13Z","closed_at":"2015-11-13T00:29:39Z","author_association":"NONE","body":"I work on a huge project. To ensue project's long-term maintainability we decided to split the application into 3 standalone pieces thus we now have 3 specialized teams. Each app exposes its own GraphQL schema. At the end we plan to create the 4th app which will merge all 3 pieces together into a `gateway` application using the `express-graphql` package.\n\n**What is the best way to merge schemas?** What we would need is a mechanism similar to [Express Router](http://expressjs.com/guide/routing.html). Our current plan is to make all 3 apps available as private packages from which we can build a new schema for the main (4th) app. Well, we could make each app act as a standalone private graphql server and then the main application would just send requests to sub-apps but I believe it could potentially represent a huge overhead. Am I wrong? \n\nAre there any plans for supporting this? What do you suggest? How do you handle this at Facebook?\n"},"comment":{"url":"https://api.github.com/repos/graphql/graphql-js/issues/comments/348031565","html_url":"https://github.com/graphql/graphql-js/issues/223#issuecomment-348031565","issue_url":"https://api.github.com/repos/graphql/graphql-js/issues/223","id":348031565,"user":{"login":"jrop","id":1404053,"avatar_url":"https://avatars0.githubusercontent.com/u/1404053?v=4","gravatar_id":"","url":"https://api.github.com/users/jrop","html_url":"https://github.com/jrop","followers_url":"https://api.github.com/users/jrop/followers","following_url":"https://api.github.com/users/jrop/following{/other_user}","gists_url":"https://api.github.com/users/jrop/gists{/gist_id}","starred_url":"https://api.github.com/users/jrop/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/jrop/subscriptions","organizations_url":"https://api.github.com/users/jrop/orgs","repos_url":"https://api.github.com/users/jrop/repos","events_url":"https://api.github.com/users/jrop/events{/privacy}","received_events_url":"https://api.github.com/users/jrop/received_events","type":"User","site_admin":false},"created_at":"2017-11-29T23:28:13Z","updated_at":"2017-11-29T23:28:13Z","author_association":"NONE","body":"@abhiaiyer91 I am curious to see the solution you developed to this problem."}}
{"actor":{"display_login":"jrop"}}