Stateless servers, searchable tool catalogs, and OAuth with mandatory PKCE — what the first stable release actually changes for anyone exposing app data to agents. A staging MCP server that worked perfectly on laravel/mcp 0.9 returns HTTP 400 on every single tools/call after a routine… Read More »Laravel MCP Just Hit 1.0. Your App Is Now an AI Tool Whether You Planned for It or Not
What it means that vector indexes now live in the schema blueprint instead of a separate AI package — and how to migrate your embeddings table the right way. A rollback migration for an embeddings table, written the way most teams have had to write… Read More »Laravel Quietly Added dropVectorIndex() to Migrations. Vector Search Is Now a Core Citizen
Why v0.11.2 requires laravel/mcp for agent tools now, what changes in your existing agent code, and whether 7.4M installs means you can trust it in production. composer require laravel/ai alone, on v0.11.2, does not install laravel/mcp. That’s worth stating precisely before anything else, because “mandatory”… Read More »Laravel’s AI SDK Just Made MCP Mandatory. Here’s What That Actually Breaks
What the new native vector search actually supports, why plain MySQL got skipped, and the workaround I’m using until it catches up. whereVectorSimilarTo() on a MySQL connection throws a RuntimeException. It always has, since these methods first shipped, and — as of the PR that… Read More »Laravel Just Shipped Native Vector Search for MariaDB. If You’re on MySQL, You’re Locked Out
Telescope query logging, N+1 elimination, Redis caching, Octane setup, eager loading strategy, queue offloading, and the database indexes we should have added on day one — a real performance audit on a real Laravel app, with before and after numbers. The number in the title… Read More »How to Optimize a Slow Laravel App: The Step-by-Step Audit That Cut Our Response Time by 73%
A real before/after audit of what automated review actually catches versus what it just flags noisily. The auth layer had already been through two rounds of human review before it went anywhere near an AI reviewer — a senior developer who’s shipped Sanctum-based APIs before,… Read More »I Rebuilt My Laravel API’s Auth Layer With an AI Code Reviewer. It Caught 3 Bugs a Senior Dev Missed
The demo always works. Here’s what breaks between a working prototype and a feature real users depend on. The number in the title isn’t a citation — it’s a rough, honest estimate from watching this pattern repeat across enough projects to notice the shape of… Read More »Why 40% of “AI-Powered” Laravel Features Get Ripped Out Within 6 Months
A developer-nostalgia piece tracing Laravel’s evolution — and why most “what’s new” posts miss the real architectural shift. The first Laravel app I ever shipped had a routes.php file with every single route in the entire application in it, a Controller.php I extended for reasons… Read More »10 Years Ago I Learned Laravel 5. Here’s What Changed That Actually Matters
Unhandled rejections, sequential vs parallel mistakes, the Promise.all trap with partial failures, async forEach that does not work the way you think, AbortController for cancellation, and the error handling pattern that catches what try/catch misses — the async patterns that actually work in production. A… Read More »JavaScript Async/Await in 2026: How to Stop Writing Code That Breaks in Ways You Don’t Expect
Performance benchmarks, hiring costs, ecosystem maturity, AI tooling support, deployment complexity, and the project types where each genuinely wins — not the Reddit opinion, the actual production experience from someone who has shipped both. Every “Laravel vs Node.js” post either declares a winner in the… Read More »Laravel vs Node.js in 2026: A Senior Developer’s Honest Verdict After Using Both in Production