graphene

> But you need to know that Wasmer and its sibling projects will stay free forever. We are open source lovers, all of us, and we have a strong background on working on open source projects before joining Wasmer too. That's great. I'm sure the closed source paid 10x faster editions of the graphene Python GraphQL server written by Syrus "CEO of Graphene" and CEO of wasmer will be open sourced in this spirit. https://github.com/graphql-python/graphene/issues/268#issuec... http://graphql-quiver.com/

That sounds awesome and also a huge headache. I've found its much easier to work with an ORM that is specifically designed for GraphQL, like TypeORM[1]. Otherwise you are just kind of trying to force a square peg in round hole (like Graphene[2] for Django). As for not exposing some data, just use "private" schema directives, etc. [1] https://github.com/typeorm/typeorm [2] https://github.com/graphql-python/graphene

> how best to use ORM with it GraphQL is not about the server-side - that's an implementation detail and is orthogonal to GraphQL itself. I think it's important that we don't conflate ORMs with GraphQL just because an ORM can be used to simplify the server-side implementation (take a look at Graphene [1] or Prisma [2]). [1] https://github.com/graphql-python/graphene [2] https://github.com/prismagraphql/prisma

> Are there any examples of a full blown GraphQL server Sure! But here's the thing to know: the meat of a GraphQL server is in the schema. Every server implementation you see will have you define a schema, and then will execute queries against it. I would do the setup for the implementation in the language of your choice (instructions for which is usually listed in the README of the git repo), and then take a look at example schema, the most famous of which is the Star Wars schema: For JS: https://github.com/jahewson/graphql-starwars For Python (Graphene): https://github.com/graphql-python/graphene/tree/master/examp... > interpreting complex queries as SQL/NoSQL queries in a performant way Something which is often confusing is that GraphQL is completely database agnostic. However you were fetching data from your database of choice before,

What part does Graphene play (assuming you mean https://github.com/graphql-python/graphene). Are you building graphql based apis rather than rest ones?

I really love the django ORM, after your model are done you can create a really fast api with DRF, and if you want to try graphql/relay is possible with graphene https://github.com/graphql-python/graphene.

For those who don't have the time to watch all the videos, here's are the github links to the most interesting projects from Day 2: NavigationExperimental: new multi-tab-aware navigation component https://github.com/facebook/react-native/tree/master/Librari... cf. previous work on in-app "paths"by TaskRabbit http://tech.taskrabbit.com/blog/2015/09/21/react-native-exam... Nuclide is an IDE for building react-native apps http://nuclide.io/docs/quick-start/getting-started/ source https://github.com/facebook/nuclide Realm is a mobile database: an alternative to SQLite & key-value stores. Previously iOS and Java, now works with react native too https://github.com/realm/realm-js Exponent lets you write apps in js w/o need for iOS/Android toolchain https://exponentjs.com/ Static site generator using React.js https://github.com/gatsbyjs/gatsby Re