2 ms·
If you're following basic REST guidelines regarding idempotency then, yes, you can "just fix it with a cache." That's the whole point of the guideline. Updates
by vinceguidry 10y ago
If you're following basic REST guidelines regarding idempotency then, yes, you can "just fix it with a cache." That's the whole point of the guideline. Updates can still take awhile, but you can fix that if you need to with a backend jobs server.
Performance should always be in your mind somewhere, but it doesn't always need to be at the forefront.
- jschwartzi 10y agoUnless it's taking 8 seconds to load because your user is on 2G. Then the only way you can avoid that hit is by not making the requests in the first place.
- brianwawok 10y agoWell, or sending very compressed binary data to the user and rendering more client side, vs sending fat HTML on every click.