3 ms·
> decades of best-practices and standard ways to do (...) caching Essentially either you want RPC, or you might want caching. If you want to put a varnish cach
by e12e 5y ago
> decades of best-practices and standard ways to do (...) caching
Essentially either you want RPC, or you might want caching. If you want to put a varnish cache in there, probably stick with http. If you know you're doing (very high thro / low latency) RPC - this might make a lot of sense.
- VWWHFSfQ 5y agoWhat if I want to memoize my RPC function though? I would have to implement that myself I think
- e12e 5y agoIf your messaging lends itself to caching, it might very well fit with REST - which means http might be a good option. So it's not so much if you want to memorize (cache), but if you can* (and/or should). I'm afraid I'm repeating myself - but I really whish people would read all of Fielding's thesis - it's got all kinds of reasonable architectures in it - even if it argues hypermedia/hypertext applications are well served by REST. https://www.ics.uci.edu/~fielding/pubs/dissertation/top.htm https://www.ics.uci.edu/~fielding/pubs/dissertation/top.htm