Can Laravel handle high traffic applications?

Question

I am working on a PHP / MySQL social network project, which will consist of many modules / sections, including:

• user system (permissions, profiles, settings, etc.)
• stackoverflow style icon and reputation system
• Friends Wall / Stream
• Forums
• message system
• portfolio
• The blog
• code snippets
• bookmarks
• and several other sections ...

I originally planned to build everything using the Laravel framework, as it is just awesome and also does most of the work.

Now I ask about it. I have not started the code yet, so this is not a factor in the decision.

Also, my time spent on creating any part of the site / application does not decrease performance.

So, if Laravel leads to reduced productivity and construction from scratch, but it saves a ton of time. I would rather spend a ton of extra time building from scratch if that means better productivity and a better long-term outlook.

At the end of 2006, I built a hybrid of MySpace and Facebook social networks and did not use the framework. This gave me 100% control over every aspect of everything and more performance, because I was able to really tune and optimize everything as the network and traffic grew. I think you are losing some of the low level optimization options when using a large structure?

My question can easily be mistaken as an opinion based question. However, to some extent its essence should be legitimate, how theoretically this would be the best way, if productivity will be a priority over time.

I only have a low-traffic application with an infrastructure like Laravel, so I have no experience creating a high-traffic application with a structure like Laravel, so I don’t know how well they work compared to without a frame.

All my high traffic apps were borderless.

Depending on the type of modules / partitions listed above. Can Laravel handle these types of applications at a high traffic level and at a large scale?

Answer 1

This question is a bit vague - for starters, what is the definition of high traffic?

In cases where I work, we run a combination of manual code from scratch and the areas that are served by the laravel application (this is built into the main site and provides the same amount of traffic as all the old application code).

In areas built using laravel, it has not slowed down (the same database sources are used, and it works on the same web servers, which is useful for testing).

Cautions:

The original manual code is older and does not always use the new PHP methods / design types. This means that it is not as effective as it could be. Then you have overhead when laravel does what you don’t always need / need to continue.

Summarizing

What this means is a layout that you think will be the hardest part of your application in laravel, and then again with custom code. Then compare this shit.

You will most likely find that (good) manual work will be faster. Is it worth the milliseconds? Well, it's up to a personal choice. Laravel is more than capable of handling large amounts of traffic, but of course you could shave a small amount of time without using it.

How important is what you do? If something slows it down and causes problems in Laravel, change it. This is an open source.

For reference (to you, if you consider this as high traffic or not - I would):

This is a UK based SASS that usually caters to visitors from the UK. At 9 pm tonight (Friday evening is actually one of our calmest times), we currently have about 250,000 active PHP sessions running.

The system is serviced through 6 web servers [for redundancy, traffic, etc.] (load balancing) for a PHP application.