Can you talk about how we've implemented caching? So that is a bonus advanced tip. And it is something that has worked really well for us in some applications. It's not a universal do this and it works for everything. But when you have data types that aren't being changed frequently, so a blog post, for example, well, there's really no reason for you to be constantly pulling the database for that content because it hasn't changed. And so by implementing database caching, and it's a little tricky and you have to do some work in your application to set it up and you have to be kind of know how to do it, by the way, that's going to be in a upcoming video. But it does allow you to control the data that is actually being sent to your bubble application. Bubble constantly pulls the database normally, but if you use caching, then that's not happening because it's going via an API call and once it's pulled, it can be cached in the edge server and it's not even affecting bubble. So you're actually saving money from bubble as well because you're not making use of as many workflows. Exactly.