104: Jonathan Reinink - Pushing More Work to the Database

In this episode of Fullstack Radio, I talked to Jonathan Renick about pushing more work to the database to speed up your application. This is Fullstack Radio episode one zero four. Before we get into the conversation with Jonathan today, I just wanted to quickly announce that a few days ago, Steve Shoger and I finally released refactoring UI, which is a huge package we put together that will give you everything you need to start making your projects look awesome without relying on the help of a professional designer. It includes a 218 page book, a set of video tutorials, a custom illustrated icon set, pre built professionally chosen color palettes and font recommendations, as well as a huge gallery of component and layout ideas to help you get any new design started on the right foot. Right now, it's available for 40% off. So if you haven't checked it out already, head over to refactoringui.com/book to learn more about it. Thanks. Now back to the show. Hey, everyone. Welcome to another episode of the Fullstack Radio podcast. I'm your host, Adam Wathan. And today, it's my pleasure to be welcoming back a recurring guest, Jonathan Renning. How's it going, dude? I am doing awesome. Thanks for having me back on, Adam. Awesome. So, a couple weeks ago, maybe a month or I don't know how long ago it was. Yeah. It was in November. Yeah. You you put up this article that was, basically talking about how to do some more advanced kind of database querying stuff and how to kind of make some of these little things that you need to do with like Eloquent and Laravel, for example, a lot more performant than they might be otherwise. And you also gave a talk that went into depth about a lot of this stuff at Laracon online, back in February, I think it was. Yep. So, I thought it'd be awesome to have you on the show to talk about some of this stuff because that's an area where I think, myself, like a lot of people, don't have a ton of skills and knowledge. Like, I know my way around the ORM really well. I can write SQL, you know, and get by. But when it comes to, like, really more sophisticated queries and doing stuff with sub selects and stuff that I don't even know how to write by hand, I think I have a lot to learn there. And I think there's a lot that, the listeners could could benefit from learning as well. So, yeah, so why don't you talk a little bit about just kinda your mentality when it comes to trying to solve problems like this? Because I know that a lot of people talk about, like, trying to make sure that your code is as decoupled from things like the database as possible. You know, you should be able to switch between MySQL or Mongo or some external API, you …