Newbie questions about gramps--legacy HOT 3 CLOSED

Glad to hear GrAMPS is useful for you! (Me too!!)

1. You can find the new "anatomy of a data source" here and a working example (with model/connector etc) here
2. I would personally say that we're production ready but @jlengstorf may speak into that more because he's been using GrAMPS at IBM. The API is slightly different in 1.0 but the core concepts are pretty much the same.
3. As far as I know, GrAMPS should work with all of the provided "Servers" from apollo

A simple micro server would look like this

import { microGraphiql, microGraphql } from 'apollo-server-micro';
import micro, { send } from 'micro';
import { get, post, router } from 'microrouter';
import gramps from '@gramps/gramps';
import XKCD from '@gramps/data-source-xkcd';
 
const graphqlHandler = microGraphql(gramps({dataSources: [XKCD]}));
const graphiqlHandler = microGraphiql({ endpointURL: '/graphql' });
 
const server = micro(
  router(
    get('/graphql', graphqlHandler),
    post('/graphql', graphqlHandler),
    get('/graphiql', graphiqlHandler),
    (req, res) => send(res, 404, 'not found')
  )
);
 
server.listen(3000);

from gramps--legacy.

Hey, @goluis — everything @ecwyne said is correct. We haven't put together all the examples yet, but GrAMPS returns a GraphQLOptions function that should be compatible with all flavors of Apollo server.

GrAMPS has been running in production at IBM Cloud, so it's definitely production-ready.

Please let us know if you have any additional questions! Also feel free to join the #gramps Slack channel for questions.

from gramps--legacy.

You can sign up for the Graphcool slack channel here.

http://slack.graph.cool/

from gramps--legacy.