DEV Community

Discussion on: The Return of Server Side Routing

 
fakeclifcarter profile image
Clif Carter • Edited

Thank you for replying! Yeah, I just listened to a podcast about caching:
Easy to implement. Hard to implement efficiently and correctly. Or at least it takes time to understand it in depth enough to implement correctly.

Every app is different. Learning what tech/framework/etc. will work great for you requires dedicated upfront time to research.

An upfront cost that is always worth it

Thread Thread
 
ravavyr profile image
Ravavyr

So Caching is a funny beast. I agree, it's worth implementing for many systems, but you gotta remember, with JS frameworks, much of what was once cached, can now simply be served as static sites.
So really you do very little caching, though one might say "static code" == "cached code".
Static sites would make api calls, meaning you either cache the api results or setup scalable environments for the dynamic data.

Some comments have been hidden by the post's author - find out more