Exploring Caching in Web Applications

I’ve been exploring the topic of caching in web applications lately. To be more specific, I’ve been interested on how data gets cached for better performance; especially when you’re performing really expensive queries. Maybe you’re returning a bunch of results and want to cache those results so you don’t have to request data from your database constantly.

Use Cases for Caching

  • If you’re consuming an external API, you can cache the results for a certain period of time without making a request to that API every time the page loads.
  • You’re application constantly hits your database and tries to retrieve data. If you’re in this situation, you can cache the results on your page so you don’t have to query the database every time.
  • etc.

I made a video covering what I’m going to go over in the next could videos and blog posts. I want to experiment with a situation where I have a lot of data in the database and I have a feed where it’s constantly delivering data. I want to cache this data so I can minimize queries to MySQL or Postgres. I think this will be a fun little experiment. 🙂 I’m planning to collect some data and put it visual form; making this look all professional, I just need to make sure to use a data management system as good a s the one from Couchbase. 😉

Anyway, here’s the video:

Update on Vlog

I’m still working on the vlog. I’m feeling kind of “meh” about it and I want to feel inspired when I’m working on it. I don’t want to put out crappy work. However, I am still releasing that as soon as that’s finished.


Tyler Souza

Tyler is a very passionate full-stack developer who thrives on a challenge. He specializes in programming (mainly in Python), REST API development, and keeps up with the latest front-end technologies. When not coding, he loves to eat ramen, BBQ, and travel.

You may also like...