Laravel PHP Framework Reviews

Frameworks are normally made to help people working with a programming languages they are using to work more efficiently. For example, if you want to build your system using Microsoft features, then you should go use a .NET Framework. If you want to build your system by PHP programming language, then you can use a PHP framework like Laravel.  

The primary use for Laravel Framework in my case is for my PHP development of software and my web sites.  

Laravel has helped us to more efficiently spread our workload within our development team.  

The most valuable feature is how the framework minimizes the need to use redundant code. I can reuse blocks of code and this minimizes rewriting or copying and also simplifies troubleshooting reused code.  

One thing that is not so good about this solution is that the implementation process is quite complex. To get the final output, you have to maintain a lot of extra processes or parts. If you are not careful with the system you can damage it easily.  

Because there is some dependency, these dependencies need to be added to the system. If you forget to add in any dependency, then it will not work.  

What I would like to see improved to minimize the size of the built-in system's extra processes. There are a lot of default files that bulk up the installation. I would also like the setup to be more intuitive.  

I have been using Laravel, all together, for about one and a half years.  

More-or-less, I can say that it is stable. It could perform better or more efficiently, but it may only lag and not crash.  

Obviously Laravel is scalable because that is what it was meant to be by design. In my company, there are several departments. Some work with networking, some work with software development, et cetera. In my department, there are 20 to 25 employees that are working with Laravel and other software development tools. The product is constantly in use by the entire department, but the projects and their roles in a project may be different.   

In this product, there are several features or functions. To develop a system, you do not need to do all the parts of the system by yourself. The tasks can be divided between a team of employees. So one employee will be responsible for one feature and the other on the team is responsible for another feature. In this way, all the features are covered but not by the same person at one time. A specific person is responsible for a specific part of the task. You can make the team larger or smaller to scale with production on a project.  

I do not go through support. I do use the community tools on Quora, however. There are a lot of users on the platform who discuss bug-related problems and a lot of users with experience who provide answers. There are buttons to vote for which answers are the best ones so the best answers become the best rated. It makes it easy to find the right answer and to participate in the discussions.  

I have used and am sometimes still using Core PHP, Raw PHP, and Laravel. Another thing I use on the database in a server is PHP MIME (Multipurpose Internet Mail Extensions). I have not used anything else for my PHP development.  

The initial setup is not entirely straightforward because there is some dependency. These dependencies need to be added to the system first. You have to be sure this setup is complete.  

The amount of time it takes to deploy actually depends on the system you want to build. If you want to build a simple web development system, then it may require less than two to three days to configure a small rack. But if you go for a more complex system, then it will require more effort and time. I cannot accurately say how much because it depends on the scope of the system and other criteria for usage.  

But the basic installation may not take any more than two days. If you are an amateur, then it will take more time.  

There are some things that you can handle by yourself in the installation by using the documentation they provide. In some extra or exceptional cases, you probably want to use the assistance of an expert.  

We took care of the implementation ourselves with some help through available online help resources.  

The cost is not an issue because the product we use is open-source.  

When you first build something you may create a lot of files to build a working system. If you look closely later, you may see that some files you created were redundant or unnecessary. But because you built the system it will now not support itself without those files and redundancy already created. Instead of doing this type of management, you should let Laravel help create it. It will help you manage and be more consistent and efficient.  

On a scale from one to ten where one is the worst and ten is the best, I would rate Laravel as a seven-point-five out of ten. You can round that up to eight.  

Authentication-based users and any content-related production are the primary use case, whether that be text-based or financial transaction related.

Faster development cycles with good community support and third-party packages to choose from. It keeps up-to-date with major releases of common tools, like PHP and SQL databases.

MVC Framework which Taylor built is simple to use and has many built-in features, especially on models and collections. The command-based tools are a must have. We use this feature extensively to handle numerous cron-based tasks within our applications.

• V.3 was nice to get the tool going, but it was limited.
• V.4 was much better and we rolled out numerous production applications, which still run today. 
• V.5 was neat and matured.

My main use case for Laravel PHP Framework is using it as a backend for web applications.

A quick specific example of a web application where I used Laravel PHP Framework as the backend is our in-house ticketing system for our customers so they can open support tickets.

We are using Laravel PHP Framework for integrating web applications with SQL database.

In my experience, the best features that Laravel PHP Framework offers are that it's fairly old, having been out for a long time, so there is a lot of resources on the internet, and the community is very large. The libraries are very good, allowing you to find what you need easily.

Laravel PHP Framework has positively impacted my organization by allowing us to switch from developing the same project using Java, which took much longer, to Laravel and PHP, saving a lot of time. Our project is deployed on AWS, so we used it on AWS.

Things moved twice as fast with Laravel PHP Framework compared to Java.

Laravel PHP Framework needs to be constantly updated and modernized because it is now considered legacy, and there are many more modern programming languages that are coming and becoming more famous, easier, and more attractive for today's programmers. Laravel needs to be modernized and kept trending because it's currently considered legacy and it's slowly dying.

I have been using Laravel PHP Framework for five years.

Since I'm not a programmer but a cybersecurity engineer, a lot of the code I write is mainly taken from publicly available resources, and having a good community that has a lot of similar code to what I need available easily has helped a lot compared to other programming languages.

I urge others looking into using Laravel PHP Framework to use it over other programming languages as it's been out for a long time. It has a lot of support, and they will easily find things on the internet to help them. Laravel PHP Framework is a very stable and reliable programming language that has a lot of room for creativity and can help you achieve whatever you want to do with your web application. It's very useful. I would rate this product an eight out of ten.