# Craig McInroy - Software Engineer from Eastern Canada **URL:** \ **Category:** Introduce-Yourself\ **Created:** [January 21, 2019, 8:21pm UTC](https://community.neo4j.com/t/craig-mcinroy-software-engineer-from-eastern-canada/4519 "2019-01-21T20:21:56Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![cmcinroy](https://sea1.discourse-cdn.com/flex021/user_avatar/community.neo4j.com/cmcinroy/32/2954_2.png) [@cmcinroy](https://community.neo4j.com/u/cmcinroy)\ **Post date:** [January 21, 2019, 8:21pm UTC](https://community.neo4j.com/t/craig-mcinroy-software-engineer-from-eastern-canada/4519/1 "2019-01-21T20:21:56Z")
Greetings, folks! 👋 _Really_ interested in exploring applications for Neo4j. I've been looking for discussions of the recent thinking on polyglot persistence. We've been doing a lot of GraphQL work in the past year and there are aspects of our solution that would benefit greatly from the use of Neo4j. ---
**Author:** ![neo4j\_devrel](https://sea1.discourse-cdn.com/flex021/user_avatar/community.neo4j.com/neo4j_devrel/32/18147_2.png) [@neo4j\_devrel](https://community.neo4j.com/u/neo4j_devrel)\ **Post date:** [April 23, 2019, 4:15am UTC](https://community.neo4j.com/t/craig-mcinroy-software-engineer-from-eastern-canada/4519/2 "2019-04-23T04:15:42Z")
Hi! You might have already tapped into this, but if you have not - [GRANDstack.io](http://GRANDstack.io) How is the project coming along? ---
**Author:** ![cmcinroy](https://sea1.discourse-cdn.com/flex021/user_avatar/community.neo4j.com/cmcinroy/32/2954_2.png) [@cmcinroy](https://community.neo4j.com/u/cmcinroy)\ **Post date:** [April 24, 2019, 2:22pm UTC](https://community.neo4j.com/t/craig-mcinroy-software-engineer-from-eastern-canada/4519/3 "2019-04-24T14:22:42Z")
Hi, @neo4j_devrel! Had to shelve things for a bit, but we've had a recent infusion of resources, so will be revisiting it again. Thanks for the suggestion on GRANDstack! I have seen that. I am particularly interested in resources that would help with our goal of using GraphQL to span multiple data sources that _include_ Neo4j. We're currently using Postgres and MongoDB and are working on an API gateway that spans the two, but I would love to have Neo4j in the mix! ---
**Author:** ![neo4j\_devrel](https://sea1.discourse-cdn.com/flex021/user_avatar/community.neo4j.com/neo4j_devrel/32/18147_2.png) [@neo4j\_devrel](https://community.neo4j.com/u/neo4j_devrel)\ **Post date:** [April 30, 2019, 6:37pm UTC](https://community.neo4j.com/t/craig-mcinroy-software-engineer-from-eastern-canada/4519/4 "2019-04-30T18:37:22Z")
That's pretty interesting! I'd love to know more about it when you have more of it created. 😄 ---
**Author:** ![lyonwj](https://sea1.discourse-cdn.com/flex021/user_avatar/community.neo4j.com/lyonwj/32/27358_2.png) [@lyonwj](https://community.neo4j.com/u/lyonwj)\ **Post date:** [May 2, 2019, 4:01am UTC](https://community.neo4j.com/t/craig-mcinroy-software-engineer-from-eastern-canada/4519/5 "2019-05-02T04:01:29Z")
Hey Craig - our [neo4j-graphql.js](https://grandstack.io/docs/neo4j-graphql-js.html) GraphQL integration is flexible enough to handle multiple datasources - basically you can just implement resolvers as you normally would for fetching data from Postgres/MongoDB, etc and neo4j-graphql.js will only auto-generate the missing resolvers for fetching data from Neo4j. Schema stitching the GraphQL API generated from neo4j-graphql.js would be another option - we have some users taking that approach as well. ---
**Author:** ![cmcinroy](https://sea1.discourse-cdn.com/flex021/user_avatar/community.neo4j.com/cmcinroy/32/2954_2.png) [@cmcinroy](https://community.neo4j.com/u/cmcinroy)\ **Post date:** [May 3, 2019, 3:01pm UTC](https://community.neo4j.com/t/craig-mcinroy-software-engineer-from-eastern-canada/4519/6 "2019-05-03T15:01:11Z")
Thanks, William! That's really interesting... i was _aware_ of neo4j-graphql.js, of course, but hadn't looked into the auto-generate functionality. I had been planning to go the schema stitching route, since I've used that in the past. Great to know there is another option. Thank you!