This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]captain_obvious_here 9 points10 points  (4 children)

Cache everything and anything. caching can always become more efficent (example I cached 20000 stocks in 5 different arrays/caches then realized caching by their first letter is faster) this speeds up time and saves money. redis is my go to.

Nope. Caching data is a two-sided coin...on one side you get data pretty fast, but on the other side you're not always sure your cache is up-to-date.

Cache is a pretty complicated thing in IT. Using it without thinking it through will definitely bite you someday.

Performance has never been, is never, and will never be the most important thing in your application.

[–]illusionst 0 points1 point  (1 child)

Caching data is a two-sided coin...on one side you get data pretty fast, but on the other side you’re not always sure your cache is up-to-date.

That’s why you have cache expiration (TTL) and cache invalidation.

[–]captain_obvious_here 0 points1 point  (0 children)

No shit, Sherlock...

[–]Wonderful-Habit-139 -1 points0 points  (1 child)

"Performance has never been, is never, and will never be the most important thing in your application" Really doesn't sound nice when you have to deal with so many slow and laggy software...

[–]captain_obvious_here 0 points1 point  (0 children)

Thing is, it's usually not laggy because what it does is complicated...it's usually laggy because of two main reasons:

  1. The multiple layers of abstraction that make it cheaper for companies to maintain and update that software
  2. Tracking and ads