Fast database queries are not always better

Published
Sep 2, 2023
Written by
Benjamin Crozat
0
comments
1 minutes
read

Tim MacDonald sheds new light on a commonly held belief in web development circles – that fast database queries are always good, and slow queries bad. MacDonald, an experienced developer, admitted to contributing to this confusion by failing to clearly explain a certain Laravel method.

In an interesting spin, he suggests that fast queries could actually slow down HTTP requests if they’re happening in mass in a single interaction. He then goes on to demonstrate a feature in Laravel that neatly tracks such cumulative query time, thus helping optimize resource usage.

Intrigued? Give Tim’s article a read!

About Benjamin Crozat
Benjamin Crozat

Hi! I’m from the South of France and I’ve been a self-taught web developer since 2006. When I started learning PHP and JavaScript, PHP 4 was still widely used, Internet Explorer 6 ruled the world, and we used DHTML to add falling snow on websites.

Being able to educate myself for free on the web changed my life for the better. Giving back to the community was a natural direction in my career and I truly enjoy it.

Therefore, I decided to take action:

  1. I launched this blog in September 2022 with the goal to be in everyone’s Google search. I get more than tens of thousands of monthly clicks from it and even more visits overall (my analytics dashboard is public by the way).
  2. I also started growing my X (formerly Twitter) account at the same time, which has now over 7,000 followers.
  3. All the content I write is free thanks to my sponsors.

I also want to be completely free with my time and make a living with my own products. In April 2024, I launched Nobinge, a tool to summarize and chat with your content, including YouTube videos.

Believe me, I’m just getting started!

0 comments

You need to be signed in to comment this post.
Sign in with GitHub