Back at the start of 2017, we decided to create a web-based tool for the SEO OnPage analysis of our clients' websites. We had over 2.000 websites to analyze, so we had to perform thousands of requests to get every single page from those websites, process the information and save the big amounts of data somewhere.

Very soon we realized that the initial chosen script language and database, PHP, Laravel and MySQL, was not going to be able to cope efficiently with such a task.

By that time, we were doing some experiments for other projects with a language we had recently get to know, Go , so we decided to get a try and code the crawler using it. It was fantastic, we could process much more data with way less CPU power and in less time. By using the concurrency abilites that the language has to offers, we could also do more Http requests in less time.

Unfortunately, I have no comparison numbers to show about the performance differences between Go and PHP since the difference was so clear from the beginning and that we didn't feel the need to do further comparison tests nor document it. We just switched fully to Go.

There was still a problem: despite the big amount of Data we were generating, MySQL was performing very well, but as we were adding more and more features to the software and with those features more and more different type of data to save, it was a nightmare for the database architects to structure everything correctly on the database, so it was clear what we had to do next: switch to a NoSQL database. So we switched to MongoDB, and it was also fantastic: we were expending almost zero time in thinking how to structure the Database and the performance also seemed to be better, but again, I have no comparison numbers to show due to the lack of time.

We also decided to switch the website from PHP and Laravel to JavaScript and Node.js and ExpressJS since working with the JSON Data that we were saving now in the Database would be easier.

As of now, we don't only use the tool intern but we also opened it for everyone to use for free: https://tool-seo.com

I use Laravel because it has integrated unit testing that making TDD a breeze. Having a View (Blade engine) making me easier to work without too many efforts in front-end.

I do recommend going into the root of programming once getting stable on any framework. Go beyond Symfony, go beyond PHP, go into the roots to the mother of programming; c++, c, smalltalk, erlang OTP. Understand the fundamental principle of abstraction.

A framework is just a framework, it helps in getting feedback quickly; like practicing dancing in front of a mirror. Getting fundamentals right is the one true key in doing it right. Programming is not hard, but abstract-programming is extremely hard.

I use Laravel because once a client asked me to use it, I recognized that as a solo programmer, I could go from idea to basic website in under an hour. Add one of the app builder templates and the basic design is done for me as well (I use AdminLTE). Lead management means a simple database and some basic workflow - that is where you should be spending your effort. Laravel is well-enough designed that you can plug in a few basic web pages, a simple set of object models, and some Controllers that hold your business logic - and then you iterate on the pages (the UI) and the business logic until your requirements are met. If you are a stickler or have corporate CSS standards, they can be implemented easily enough. And the community is huge and friendly.

I use Laravel because once a client asked me to use it, I recognized that as a solo programmer, I could go from idea to basic website in under an hour. Add one of the app builder templates and the basic design is done for me as well (I use AdminLTE). Lead management means a simple database and some basic workflow - that is where you should be spending your effort. Laravel is well-enough designed that you can plug in a few basic web pages, a simple set of object models, and some Controllers that hold your business logic - and then you iterate on the pages (the UI) and the business logic until your requirements are met. If you are a stickler or have corporate CSS standards, they can be implemented easily enough. And the community is huge and friendly.

For your purposes, I recommend @Laravel, or even @Symfony or @Yii, or whatever. In your use case, a framework is 100% indicated, because it will cut your boilerplate in half or more, and you'll have a pre-fab organization for files, classes and so on. Personally, I am not a fan of Frameworks, because they tend to take over your project like cancer and trap you. But for an internal app to manage stuff, it's probably the best idea to use one (preferably one you like).

When doing internal apps, your best bet is to stick the essentials and basics, try Laravel with MySQL on a nice Debian virtual machine. Can't go wrong.

If you are going to build from scratch use Laravel, because it is a little easier to learn than Symfony. They have a bunch of great videos to help you along the way. If you know Drupal 8 already, that is built on Symfony and you can harness the backend, but it is going to have a steeper learning curve. On the plus side you can take advantage of all its features. I wouldn't recommend building without a type of framework. Thousands of man hours have gone into those things for a reason. I started learning Symfony w/o Drupal but lost interest once I found out how much easier Laravel was. They both have their advantages and disadvantages, laravel actually uses part of symfony in its code. I like the blade template system better than twig is a big factor in deciding as well. They are both very similar, but blade is closer to native PHP which makes it a little easier to learn.

I use Laravel because right now it's really hard to find someone using native PHP without a framework. Also learning a framework easier than native for newcomers. Also; I was not supporting frameworks before but after start developing a core with one I saw i can find many new people for the projects.

I use Laravel because you don't have to re-invent the wheel when compared to core PHP. We can focus directly on business logic. And the little learning curve for Laravel is worth it. Can't really compare with Laravel with Symfony as I haven't worked with Symfony yet. My suggestion would be to pick one and stick to it. If at all you have to move to other, it should be easy. Last thing I would like to add is that there are more people around who knows Laravel compared to PHP, may be that's why I started with Laravel.