7 ms·
Why oh why oh why do you want a stateful read? That will be the beginning of the end for your architecture.
by richardwhiuk 10y ago
Why oh why oh why do you want a stateful read? That will be the beginning of the end for your architecture.
- tdriggs 10y agoLogging/analytics? Paywalls?
- int_19h 10y agoBecause applications have state. In fact, the vast majority of reads in any applications are stateful (the database backing your app is also state, you know; I'm not talking just about session state here). By "pure" here I mean that we're talking about a pure function of its inputs.
- icebraining 10y agoWhy do you need to distinguish between those? In fact, if the function is pure, why not run it on the client?
- int_19h 10y agoBecause the server has more computational resources, for example. It's a very rare scenario in general, but it does happen. Why distinguish? Because if you know that the results are not affected by server state, they can be cached much more aggressively.
- jandrese 10y agoYou mean like a cursor in a database?
- nippoo 10y agoRate limiting APIs?