Relay Modern: Simpler, faster, more extensible

> "Relay Modern is designed from the start to support garbage collection — that is, cache eviction — in which GraphQL data that is no longer used by any views can be removed from the cache"

Could we go ahead and implement proper caching as HTTP would do: expiration date per field/models, then eviction based on expiration dates? With an optional max cache size using LIFO, last used or the current model.

That way we don't need to refetch data if the API is set up to cache. It's sort of frustrating that staleness is just defacto ignored by UI right now.

Re: Relay Modern: Simpler, faster, more extensible

#5

Post by weixiyen » Tue, Apr 18, 2017, 8:26 PM UTC

jankassens wrote: post #3

Hey, Jan here together with Lee from the Relay team. Happy to answer your questions.

Thanks Jan. Will there be support for websockets?

Re: Relay Modern: Simpler, faster, more extensible

#6

Post by StreamBright » Tue, Apr 18, 2017, 8:37 PM UTC

Is there any great libraries to implement the backend for GraphQL? I think the benefits of using GraphQL on the frontend are pretty obvious, however last time I checked I had trouble of finding good documentation or implementation on how to serve GraphQL requests from the backend point of view.

Re: Relay Modern: Simpler, faster, more extensible

#7

Post by schickling » Tue, Apr 18, 2017, 8:43 PM UTC

I'm super excited about this release! Great work Jan, Lee, Joe and everybody else who was working on this! :)

At Graphcool (https://www.graph.cool/) we were using Relay since the very beginning. It has enabled us to build frontend products at an incredible speed and while staying confident about the data layer. For instance our entire console is written using Relay at its core. (It's open-source btw: https://github.com/graphcool/console)

PS: We're also the authors of Learn Relay (https://www.learnrelay.org/) which we'll update to Modern Relay soon!

Re: Relay Modern: Simpler, faster, more extensible

#8

Post by superquest » Tue, Apr 18, 2017, 8:45 PM UTC

StreamBright wrote: post #6

Is there any great libraries to implement the backend for GraphQL? I think the benefits of using GraphQL on the frontend are pretty obvious, however last time I checked I had trouble of finding good documentation or implementation on how to serve GraphQL requests from the backend point of view.

Graphene is nice for Python. Supports Relay stuff too (I've never used these features, though).

http://graphene-python.org/

Re: Relay Modern: Simpler, faster, more extensible

#9

Post by weeksie » Tue, Apr 18, 2017, 8:47 PM UTC

StreamBright wrote: post #6

Is there any great libraries to implement the backend for GraphQL? I think the benefits of using GraphQL on the frontend are pretty obvious, however last time I checked I had trouble of finding good documentation or implementation on how to serve GraphQL requests from the backend point of view.

Absinthe works great for me: http://absinthe-graphql.org/

Re: Relay Modern: Simpler, faster, more extensible

#10

Post by orta » Tue, Apr 18, 2017, 8:50 PM UTC

Congrats! Relay is what really sold our iOS-only native team to move to React Native. Very excited to migrate to modern version at some point in the future.

( http://artsy.github.io/blog/2017/02/05/Retrospective-Swift-a... )