Gijo Varghese
02/18/2018, 10:54 AMandre
02/18/2018, 10:55 AMGijo Varghese
02/18/2018, 11:07 AMandre
02/18/2018, 11:08 AMGijo Varghese
02/18/2018, 11:08 AMGijo Varghese
02/18/2018, 11:08 AMandre
02/18/2018, 11:09 AMandre
02/18/2018, 11:09 AMGijo Varghese
02/18/2018, 11:10 AMGijo Varghese
02/18/2018, 11:11 AMGijo Varghese
02/18/2018, 11:11 AMandre
02/18/2018, 11:11 AMPrisma
has an internal caching mechanism built-in though. It is memory only and not based on an external system,Gijo Varghese
02/18/2018, 11:12 AMandre
02/18/2018, 11:12 AMGijo Varghese
02/18/2018, 11:12 AMGijo Varghese
02/18/2018, 11:13 AMandre
02/18/2018, 11:13 AMdataloader
, you can find the Graphcool library here: https://github.com/graphcool/http-link-dataloaderGijo Varghese
02/18/2018, 11:14 AMandre
02/18/2018, 11:14 AMandre
02/18/2018, 11:14 AMGijo Varghese
02/18/2018, 11:15 AMGijo Varghese
02/18/2018, 11:18 AMGijo Varghese
02/18/2018, 11:18 AMandre
02/18/2018, 11:19 AMcontext.db
calls and goes to the Prisma service. That is the approach I would suggest: Write an own layer that uses conext.db
and your Redis caching implementation
and utilize that in your resolver functions.Gijo Varghese
02/18/2018, 11:29 AM