Lumen is dead. Long live Lumen.

You’ve already read the title, so I’ll just say it, I think Lumen is dying, if not already dead.

Now let me tell you why…

Limited adoption

As the creator of Laravel Shift I get a unique pulse on the Laravel community. Something I noticed is the ratio of Laravel to Lumen Shifts is pretty staggering — about 500 to 1. At first, you may attribute this to selection bias. However, similar ratios can be found on Packagist.

The Laravel Framework currently has around 20M downloads, while the Lumen Framework has around 125k. That’s a ratio of 160 to 1. Now these are overall numbers and Laravel has been out longer than Lumen.

Despite all these disclaimers, the download charts draw the same conclusion. The ratio between their scale is still 100 to 1.

Chart: Laravel Downloads
Chart: Lumen Downloads

Less focus

Lumen also has a smaller feature set. To be fair, this is by design, as Lumen caters strictly to API development. However, while I personally agree with this direction, I think developers eventually find this restrictive. Once they hit this barrier, they are forced to switch to Laravel.

The shift to stateless APIs in Lumen 5.2 is a perfect example of this. Although this decision was clearly inline with the direction of the Lumen Framework, as a developer you were forced to limit your Lumen application or convert to a Laravel application.

I expect Lumen’s feature set will continue to lessen. Relative to other Laravel projects, it’s clear that Lumen has taken a backseat. This is evident by the documentation often referring to Laravel and the release cycle falling weeks after Laravel releases. In fact, since version 5, there have been only 10 Lumen releases compared to 132 for Laravel.

Not so fast

Finally, one of the largest proponents for using Lumen is its performance. It still beats most other frameworks (Laravel included). However, Laravel is speeding up. We see from Taylor’s recent benchmarks Laravel (without sessions) pushes 600 req/sec. This is still a third of what Lumen touts — around 1900 req/sec.

Nonetheless, I’m sure with additional optimizations one could improve Laravel’s performance if 600 req/sec was preventing them from converting from Lumen. In addition, I wouldn’t be surprised to see a few configuration options added to Laravel to facilitate Lumen-like performance boosts.

For these reasons I say Lumen is dead. But I believe Lumen will live on — just not as a separate framework. Instead, I expect Lumen will be rolled back into a future version of Laravel.

Need to convert Lumen to Laravel? The Lumen to Laravel Shift is now available to help you convert your Lumen project to Laravel.


Originally published at jason.pureconcepts.net.

Show your support

Clapping shows how much you appreciated Jason McCreary’s story.