Translations with Laravel and Inertia
This episode is for members only

Sign up to access "Translations with Laravel and Inertia" right now.

Get started
Already a member? Sign in to continue
Playing
09. Caching translations

Episodes

0%
Your progress
  • Total: 57m
  • Played: 0m
  • Remaining: 57m
Join or sign in to track your progress

Transcript

00:00
Every time we access the translation props which drive the translations that we've got, we're actually reading files. Now, this isn't great for every single request. This is going to take a little bit longer and the more and more files that you add to your translations, the slower this is going to get. So really what we want to do is cache this
00:20
so it doesn't make a request to our files or read these files every single time. So we're going to make a really simple change here just to cache everything that we're grabbing here so this speeds things up. Now, we can go ahead and monitor this. We can either use something like debug bar or in this case
00:36
just look at vet check XHR or our all tab. At the moment, we obviously don't have a very slow page load, but you can always monitor that there as well. Okay, so let's go ahead and cache this. Now to do this what we're going to do is use the cache helper. You might also want to configure how you're caching things. At the moment, our cache driver is just set to file.
00:57
This might be something set to something like Redis. It really doesn't matter, but either way it's going to speed it up. So we're going to go ahead and use the cache helper and we're going to remember this forever. You can change this just to remember this for a certain amount of time, but I think for translations, when these do change, you're going to deploy this and have your cache cleared on your
01:16
deployment anyway, or you can manually clear these. So I'm just going to go ahead and say we want to remember these forever because they're not something dynamic that changes based on user input. So in this we're going to go ahead and pass in a closure and we're just going to return here. We need to add a key in here. That's really important, of course. We're going to return everything that we've done in here.
01:37
So we're just going to grab our entire collection that we have in here that is being returned and that will do it. Now we need to come up with a cache key. We can't do something like translations because that's going to cache this for one time and that could be English or German and we're actually going to end up with an issue here. So we need to append onto this. Just to give you a demo of this, if we just give this a refresh now,
01:59
we're on German, but when I switch to English, it doesn't change because the cached version now contains German. So we're just stuck with the German language in there. So we're going to append onto this a cache key and of course, that's going to be the current locale that we're working with. So we're just going to say app get locale and that should be it.
02:19
So now we have a unique cache key for each locale that contains all of them translations. So English works, German works, and although we can't really notice at this point, it is a lot faster because we're caching them values and we're returning them from our cache. Now, of course, the only issue with this is if you add more translations, particularly while you're developing,
02:41
these are not going to show up. You can either disable the cache on development, or if you need to clear the cache at any point, you're just going to run phpr to send cache clear. That's going to clear it out for you on the first load. That's going to refetch them and then subsequent requests will just return the cached translations.

Episode summary

In this episode, we're tackling a pretty important optimization: caching translations. Right now, every time our app needs to translate something, it reads the translation files from disk. That might not seem like a big deal with just a few files, but as your app grows, this can slow things down a lot.

So, what do we do? We walk through setting up a simple cache for our translations. We'll use Laravel's cache helper (with your choice of backend: file, Redis, etc.), and we'll show you how to store the translations "forever" (or for as long as you want). That way, we're not constantly reading from files—which makes everything snappier.

You'll see us handling things like cache keys—making sure to include the current locale so German, English, and any other language get their own set of translations. And we show you what happens if you don't do that, just so you can see why it's necessary!

We'll also quickly cover how to clear the cache if you add more translations while developing, so you don't get stuck seeing old language data. By the end, your translations will be blazing fast, with just a bit of code change.

Episode discussion

No comments, yet. Be the first!