{"id":406,"date":"2025-08-27T21:03:20","date_gmt":"2025-08-27T21:03:20","guid":{"rendered":"https:\/\/1v0.net\/blog\/?p=406"},"modified":"2025-08-27T21:03:21","modified_gmt":"2025-08-27T21:03:21","slug":"how-to-speed-up-laravel-with-database-indexing","status":"publish","type":"post","link":"https:\/\/1v0.net\/blog\/how-to-speed-up-laravel-with-database-indexing\/","title":{"rendered":"How to Speed Up Laravel with Database Indexing"},"content":{"rendered":"\n

How to Speed Up Laravel with Database Indexing<\/strong><\/h2>\n\n\n\n

As your Laravel app scales, database queries often become the bottleneck. A single missing index can slow down a query from milliseconds to seconds. Indexing helps the database find rows faster by creating lookup structures on columns. In this guide, we\u2019ll cover different types of indexes, how to create them with migrations, and how to verify performance improvements.<\/p>\n\n\n\n

<\/div>\n\n\n\n\n

1 – Why Indexing Matters<\/strong><\/h2>\n\n\n\n

Without indexes, databases must scan entire tables to find records. With indexes, searches are optimized like looking up words in a dictionary. The bigger your tables, the more critical indexes become. For high-traffic Laravel apps, indexing is as important as caching and queues (see 10 Proven Ways to Optimize Laravel for High Traffic<\/a>).<\/p>\n\n\n\n

<\/div>\n\n\n\n\n

2 – Adding Indexes in Migrations<\/strong><\/h2>\n\n\n\n

Laravel migrations make it easy to add indexes when creating or modifying tables.<\/p>\n\n\n

\/\/ database\/migrations\/2025_08_27_000001_add_indexes_to_users.php<\/span>\nuse<\/span> Illuminate<\/span>\\Database<\/span>\\Migrations<\/span>\\Migration<\/span>;\nuse<\/span> Illuminate<\/span>\\Database<\/span>\\Schema<\/span>\\Blueprint<\/span>;\nuse<\/span> Illuminate<\/span>\\Support<\/span>\\Facades<\/span>\\Schema<\/span>;\n\nreturn<\/span> new<\/span> class<\/span> extends<\/span> Migration<\/span> <\/span>{\n    public<\/span> function<\/span> up<\/span>()<\/span>: void<\/span>\n    <\/span>{\n        Schema::table('users'<\/span>, function<\/span> (Blueprint $table)<\/span> <\/span>{\n            $table->index('email'<\/span>);\n            $table->index(['first_name'<\/span>, 'last_name'<\/span>]); \/\/ composite index<\/span>\n        });\n    }\n\n    public<\/span> function<\/span> down<\/span>()<\/span>: void<\/span>\n    <\/span>{\n        Schema::table('users'<\/span>, function<\/span> (Blueprint $table)<\/span> <\/span>{\n            $table->dropIndex(['email'<\/span>]);\n            $table->dropIndex(['first_name'<\/span>, 'last_name'<\/span>]);\n        });\n    }\n};<\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
This migration adds a single-column index on email<\/code> and a composite index on first_name + last_name<\/code>. The database can now quickly locate users by email or full name.<\/p>\n\n\n\n\n
<\/div>\n\n\n\n\n
3 – Unique Indexes<\/strong><\/h2>\n\n\n\n
Indexes can also enforce uniqueness, preventing duplicate values.<\/p>\n\n\n
\/\/ database\/migrations\/2025_08_27_000002_add_unique_index.php<\/span>\nSchema::table('users'<\/span>, function<\/span> (Blueprint $table)<\/span> <\/span>{\n    $table->unique('username'<\/span>);\n});<\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
This ensures no two users can have the same username<\/code>. The index speeds up lookups and enforces integrity at the same time.<\/p>\n\n\n\n\n
<\/div>\n\n\n\n\n
4 – Full-Text Indexes<\/strong><\/h2>\n\n\n\n
For searching text columns, use full-text indexes. Supported in MySQL and PostgreSQL, they allow fast search with MATCH ... AGAINST<\/code>.<\/p>\n\n\n
\/\/ database\/migrations\/2025_08_27_000003_add_fulltext_index.php<\/span>\nSchema::table('posts'<\/span>, function<\/span> (Blueprint $table)<\/span> <\/span>{\n    $table->fullText('content'<\/span>);\n});<\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
This lets you query posts with natural language search, far faster than scanning every row. For complex searches, combine full-text with Laravel\u2019s query builder filtering techniques<\/a>.<\/p>\n\n\n\n\n
<\/div>\n\n\n\n\n
5 – Measuring Query Performance<\/strong><\/h2>\n\n\n\n
Always measure performance before and after adding indexes using EXPLAIN<\/code> in MySQL\/Postgres.<\/p>\n\n\n
EXPLAIN<\/span> SELECT<\/span> * FROM<\/span> users<\/span> WHERE<\/span> email = 'test@example.com'<\/span>;<\/code><\/span>Code language:<\/span> SQL (Structured Query Language)<\/span> (<\/span>sql<\/span>)<\/span><\/small><\/pre>\n\n\n
Before adding the index, this query requires a full table scan. After the index, the DB uses an indexed lookup, which is dramatically faster on large datasets.<\/p>\n\n\n\n\n
<\/div>\n\n\n\n\n
6 – Indexing Best Practices<\/strong><\/h2>\n\n\n\n