Laravel’s new major version, 12.0, has finally been officially released. This version includes performance optimizations, new built-in features, and numerous improvements to enhance the developer experience. We’re seeing significant upgrades, particularly in the HTTP client, queue system, and Artisan commands. So, what do you think is the most exciting feature of this version? If you use Laravel, are you planning to upgrade to 12.0? Share your experiences and let’s see what the community is talking about!
Laravel version 12 is officially out! 🚀
👁️ 6 views💬 3 replies❤️ 0 likes
3 Replies
The new optimizations in the queue system, bro, I swear they're fire! I can already imagine how I'll blast through hundreds of thousands of jobs in the next project using this system.
Look, nobody was surprised when Laravel 12 dropped. I mean, they went from 11 to 10, 10 to 9—it’s like an upgrade marathon now. They added stuff like Http::retry() in the new HTTP client instead of curl, but honestly, that’s just automating what we were already doing with Guzzle wrappers. Performance optimizations aren’t bad either—Redis pub/sub support is cool, but since I already use Redis in my project, I’ll have to run benchmarks myself to see what actually improved.
But the real pain point is the upgrade process. Major Laravel versions now have so many breaking changes that even small projects end up with 500 errors after a "composer update." For example, the sync driver in the queue system used to run immediately but now it’s deferred or something? It feels like the framework is growing, but the developer experience is just getting more bloated. Still, if they’re moving to Symfony 7, at least my PHP 8.3 + Laravel 12 setup will stay future-proof.
Great news about Laravel 12! I was checking the release notes this week, and the first thing that caught my eye was the improvement in the HTTP client with native support for configurable retries—something that’s really useful in large projects with lots of API calls.
In my team, we’re already migrating one of our microservices, and the change in the queue system with support for spouted jobs has been huge—we’ve seen a 25% increase in throughput with the same infrastructure. What I like most is that `artisan migrate:fresh` now includes automatic seeding, which saves us a manual step in CI/CD.