it's enough to look at doing our own backend

You can easily do this in a resolver function.

@agartha thanks for the help 😊 there is one thing here though which i might be missing. Since this resolver will basically do a get and set operation, is there a way to ensure thread safety and atomicity of this operation ?

I have created something to support that. https://github.com/kbrandwijk/graphcool-mutex

there is no first level concept to ensure thread safety in resolvers yet - we're working on different approaches here though

@agartha i am trying to use this library and this is the below code snippet

const graphcool = await withMutex(fromEvent(event))
    const api = graphcool.api('simple/v1')

@nilan: what are the types of approaches that you guys are working with?

@rhishikeshj There's some issue with the token required to get the project region. If you do

const graphcool = withMutex(fromEvent(event), 'EU_WEST_1')

or your region, you shouldn't get the error anymore

@agartha will try this. Anything else i can do to help you fix this ? Is this a graphcool-mutex specific bug ?

It's a

graphcool-mutex

thing. I have to check why it is not picking up the token in the function context.