Only that with the right build in place I don't see why you can't go larger than 10k or handle frequent updates.
-
-
Replying to @kurtiskemple @mcrittenden
Man, I'd love to statically render Spectrum...
1 reply 0 retweets 1 like -
Fastly + surrogate key cache busting. Graphql makes it easy to generate the surrogate key list. Edge side includes may also be helpful.
1 reply 0 retweets 2 likes -
I've thought about this so often but haven't had the time to investigate properly. Is there an existing solution add all those keys based on ID fields in all returned records or something? Where are the edge cases?
1 reply 0 retweets 1 like -
Yep. IDs is where you start. Object fields may need to be added for more granularity. Edge case is you over bust and the whole thing isn't worth it
. It can also be a bit hard to debug.1 reply 0 retweets 1 like -
Could probably just use Apollo's `getDataIdFromObject` or whatever that method is called to add the __typename too, now that I think about it. Did you run this at Bustle or somewhere?
1 reply 0 retweets 1 like -
did at one point, but during last rewrite it got cut cuz of priorities. Later we revisited but decided not worth it. Bustle is much more static that spectrum so easier to cache aggressively. There is still some fancy cache busting and rererndering but not based on surrogate
1 reply 0 retweets 2 likes -
I see I see, makes sense. This is kinda what setting the surrogate keys would look like, right?https://gist.github.com/mxstbr/1a7411caa906c619f2bf7c78f0c161ed …
1 reply 0 retweets 0 likes -
Yep! You got it
1 reply 0 retweets 1 like -
Replying to @southpolesteve
Did you also use Fastly to cache GraphQL API responses? Can it even handle those?
1 reply 0 retweets 1 like
Yes in past. Fastly can handle. But currently uses API gateways built in caching for simplicity.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.