martinszeltins's avatar

Why is Symfony recommended for large and complex applications?

I was reading some "Laravel vs Symfony" comparison articles and almost all of them had a similar conclusion at the end and I wonder why? Why do most people say that Symfony should be chosen for larger and more complex applications instead of Laravel? What are you thoughts about this?

Here is what some articles said...

... Symfony is mainly used for complex enterprise projects...

Symfony is the best option if you’re building a complex enterprise application, as it is very scalable, maintainable, and well structured.

Symfony is a good choice for complex web projects, as its custom functionality works well with the requirements of your business web application.

unlike Laravel Symfony represents a more complex framework that is harder to learn, though it better works for big-scale projects.

Symfony ... is most frequently selected for large, complex projects.

Symfony contains reusable components, which provide more modularity. It organizes the code in a cleaner way, making it a great fit for larger and more complex projects.

0 likes
7 replies
jlrdw's avatar

In the background in symfony, cakephp, yii2, laravel, etc, you have regular php driving everything.

Ask yourself this, why do State Governments, very huge enterprise (Fedex), etc normally use Java technologies, also Banks.

Why are many large programs that process mass payments written in COBAL.

Honest, I wouldn't worry about that article, forget about a framework, look at the parent language. All of the frameworks I mentioned can do the same thing.

I have a custom php framework that I have kept up to date, I can easily switch to Doctrine ORM if I needed. But I have no need, but I have used Doctrine, also SAP, MS SQL, etc.

Bottom line, the language is what's most important, not the framework.

sr57's avatar

As soon as you work with other on the same project, and in fact even when you work alone :-) , you have to define common rules and Symphony is less flexible than Laravel, so it seems to be good for this.

But in fact it's more due to the fact than Symphony is older to Laravel.

And don't forget that Laravel uses Symphony components.

Bugover's avatar

The first and most important reason is ORM, Doctrine is head and shoulders above Eloquent, they are simply not comparable The second is, of course, the modular architecture of components, unlike Laravel, which is created as a monolith... Of course, I cannot describe here all the advantages of Symfony, but they are quite significant.

Laravel just has a very strong PR campaign.

1 like
martinszeltins's avatar

@Bugover Could you give specific examples why Doctrine is "head and shoulders above Eloquent" and why why a monolith in this case is worse than Symfony? Would like to hear more concrete examples why one is better than the other.

jlrdw's avatar

@martinszeltins read point 5 here: https://www.linkedin.com/advice/0/what-some-best-practices-using-laravels-eloquent

I use eloquent sometimes but prefer writing regular PDO SQL queries the majority of the time.

I have seen questions where the eloquent queries are way out there, Instead of querying a query some try to pack too much into one query.

Many times I refer people to https://www.mysqltutorial.org/

To learn some basics of structuring a query.

1 like

Please or to participate in this conversation.