Based on my experience overall, all of the things require me to write a .NET application, API6 these days, the gateway one, gRPC specifically to have a microservice orchestrator. The same thing applies for a new UI, a new IDE such as Rider. I should mention the tools I use. Apart from that, the technology is .NET, the new 9 version and all the dependencies that come with it. There are a lot actually. I am using front end React technologies with the new libraries that have better OS. That is a new library that I found out which works so well. The other things are the daily routines, the .NET dependencies and .NET. The new thing that I know is API6 as a gateway and microservice architecture, Kubernetes, and maybe Postgres database if I have to mention creating an MCP based on the DeepSeek for file management, for the users, what the application actually does and how some of the services are implemented, which are internal for the company. Those are what I have on top of my head.

Of course, I use Laravel PHP Framework for other projects which are still beyond the year. But mostly I am using a .NET framework, which sticks to Microsoft. The others depend on customer need. When I need the application to be implemented by these technologies, I should know it and dive into it and make available the solution they are looking for. I know Laravel PHP Framework because I wrote one of the social media applications here in Ethiopia, a dating application. The backend is already managed by that one, the admin panel. I have experience with these technologies.

Laravel PHP Framework is something I have been working with for almost two years because before that, I knew CodeIgniter if I understand that technology. Since I graduated, I know how to write PHP which is a pure one, and CodeIgniter came and I stuck with CodeIgniter. From the PHP side, when people demand having Laravel PHP Framework, I try to make myself familiar with it and make that admin panel.

Specifically, I am using Laravel PHP Framework for the RESTful APIs. That RESTful API was cleanly structured in order to make that, the one that I told about, the ORM. It has its own ORM, so having all the backend required implementations to make that admin panel available, it has its own OS. It uses a domain-driven application. All the domains are there. The eloquent ORM is there. The database is MySQL. For OS, for normal business logic, and for some items such as an e-commerce platform, which specifically means since they are selling different kinds of coins, I put those things as a platform. It is a kind of a mini e-commerce just to make them available on it. For some other applications, I have an API which acts as an API gateway and at the same time an API for each request from the user. Because I have a separate application called the mobile one, and whatever requests come from it should reply according to the use cases.

To be honest, because I mostly spend my time on .NET, I have all the features that I need on Laravel PHP Framework. It has its own Swagger which I can easily integrate with it. It has a webhook for making it available with Stripe. The ORMs are so flexible specifically to have N+1 problem preservations. It has authentication and authorization which is pretty okay for a developer to make things so easily. The same thing applies with having email management for the queue because people are requesting for any of their support. Webhook handling, report generation and many other features are what I have reviewed in the application.

As a .NET developer, I just go from Entity Framework to that one. It is a super set which is already set. On the users, whenever I get the posts, I can easily manipulate to have database applications by the unexisting features that are binded by an array of objects. For example, update, since the entity is already known by that one, I update these specific models according to these properties. Create such events, such posts by this one. Tracking the logs. This flexibility has already been there in Entity Framework and it is quite already similar to that one except the operations are called by the array keywords and the object mappings. At the same time, it is so speedy according to the demand.

Since I am not developing the entire applications, but I was requesting the guards and the tenant things to be right on the APIs. The simple one just makes it available login, registration, password confirmations, and based on the routing which I already set or which the identity server set. It is simple, I can make it login or guard this thing. Those are the features that I specifically use it.

Since I am not a high expert on this specific thing, I just go to the application because of the project. I do not have any specifically what should be enhanced there, but it fulfills our demand according to the requirements.

Since last year, which means the beginning of 2025, none of the projects was requiring Elastic Search.

I see it this way: when I have Laravel PHP Framework, I have a toolbox. The entire toolbox. What I have in CodeIgniter is I am expected to depend on the third libraries. For each tool, I have to buy each tool by my own or I have to implement the tools by my own. But when I come to Laravel PHP Framework, it compiles most of the items, most of the development required items and compiles it as a single toolbox.

As a .NET developer, I just go from Entity Framework to that one. It is a super set which is already set. On the users, whenever I get the posts, I can easily manipulate to have database applications by the unexisting features that are binded by an array of objects. For example, update, since the entity is already known by that one, I update these specific models according to these properties. Create such events, such posts by this one. Tracking the logs. This flexibility has already been there in Entity Framework and it is quite already similar to that one except the operations are called by the array keywords and the object mappings. At the same time, it is so speedy according to the demand.

Except from the Elastic Search or which specific product I am looking for, I am not working with any other solutions or technologies that I have good hands-on within the last 12 months this year. I had an experience working with the Elastic.

Maybe since the community size, I am not sure about how the community is fast. When I am looking to implement additional libraries, in Ethiopia, I am having my own calendar libraries. In order to integrate that, one of the developers had a little bit challenging time to make it happen on Laravel PHP Framework, since he finalized it. The flexibility or the extension to have a new library on top of it might not be that well documented. Maybe I do not know, that is what I see on the daily stand-ups.

As a .NET developer, because I highly favor .NET, I rate it as nine, but Laravel PHP Framework maybe around seven. It is just an exposure actually because I know each and each in and out of the .NET technologies, but not Laravel PHP Framework. Maybe that is where I am comfortable with. The only recommendation that I have is this is the one model which is working well for the company of our client. Start small and when it gets bigger, Laravel PHP Framework would be advisable. If someone explained to me regarding PeerSpot, I would be happy. My overall rating for Laravel PHP Framework is seven.

My main use case for Laravel PHP Framework is that I am also a freelance software developer, so I use it for building websites and web platforms, back offices, and similar projects.

While it depends on the project, I mainly use Laravel PHP Framework for websites and web apps.

A quick specific example of a project where I used Laravel PHP Framework is my personal website; I used the TALL stack, so Laravel, Livewire, Tailwind, and Alpine, with a back office made in Filament PHP. I am also a teacher of Laravel coding.

The best features Laravel PHP Framework offers are its ecosystems, including the related packages that transform how I develop things with it. Its structure and scaffolding are very complete and easy to use.

The ecosystem and scaffolding of Laravel PHP Framework have helped me significantly in my projects; for instance, all the authentication packages of Laravel are very important in my job. I have used mostly Fortify but also Laravel Breeze, and both of these packages are essential for the structure of a website. Additionally, tools like Laravel Nova and Filament PHP are great for creating back offices and admin panels. I also speak at the Italian Laravel Day, which is a convention focused on Laravel, and the community around the framework is incredible.

Other standout features about Laravel PHP Framework community include Laracasts, a website where I can find numerous workshops, videos, and webinars about the Laravel world, all of very high educational quality, and for its cost, it is really a bargain.

Laravel PHP Framework has positively impacted my organization because it is very easy to use and master while providing incredible control over everything. It is also very safe, built upon important features of cybersecurity, making it a sound foundation for web development in general and for web applications.

I do not think there is really any room for improvement in Laravel PHP Framework because it is pretty much perfect. The Laravel team does a great job renovating the framework every year, and while it could perhaps better incorporate other languages that are not PHP, like JavaScript frameworks, it does a really good job as it stands.

I do not have anything on the table right now regarding needed improvements.

I have been using Laravel PHP Framework for five years.

Laravel PHP Framework is definitely stable in my experience.

The scalability of Laravel PHP Framework is great; with the right tweaks, I can build a very simple and smooth website, as well as a complex e-commerce site or a CMS. It is very easy to use it in different ways, which is something I really appreciate about it.

There is no formal customer support for Laravel PHP Framework, but the community is very active, and I honestly have not had any problems with Laravel.

Before using Laravel PHP Framework, I used to develop in HTML, CSS, and JavaScript, and I also tried developing something in ReactJS or similar frameworks. However, Laravel PHP Framework is too comfortable to use, making it hard for me to use other solutions; it is perfect for my needs.

Although I cannot provide specific outcomes or metrics, working with Laravel PHP Framework has allowed me to deploy a website in maybe two weeks instead of months. It is a very easy-to-use framework that gives access to many important features which, without Laravel PHP Framework, I would have had to develop by hand. I can think of Laravel PHP Framework as a tool shed where everything is organized, and I just have to choose the right tool for the right job.

I do not have something specific in terms of return on investment metrics, but I have surely reduced time and employees; and for me as a freelancer, the fact that I do not have to pay for the technology means that everything I gain from my clients goes entirely to my profit, since I do not have to pay for any technology stack.

My experience with pricing, setup costs, and licensing for Laravel PHP Framework is that it is totally free, making it a win-win situation.

I evaluated other options including ReactJS and Vue.js before choosing Laravel PHP Framework.

My advice to others looking into using Laravel PHP Framework is to check out Laracasts videos to understand what the framework is and how it works. PHP is more alive than ever, despite what certain memes suggest.

I believe that everyone wanting to learn how to code, do web development, or step up their web development skills needs to evaluate Laravel PHP Framework and consider it. I rate this review as a ten out of ten.

We have multiple projects built on Laravel PHP Framework; as of now, we have nine to ten projects. That's something we can do with respect to what is required in web development, process, or functionality.

We complete web apps using Laravel PHP Framework. The complete web app, from A to Z, we can completely develop on Laravel for APIs, as well as complete, robust applications. We can completely deploy it with Laravel.

We are using Laravel PHP Framework in several AI projects with APIs. For the back end, we have a Python server especially to handle all the AI requests which we receive. We don't directly connect the AI with our Laravel application, but we have a dedicated server which we have written in Python technology that we use with that.

I find the command line interface very valuable in Laravel PHP Framework, for instance, the migrations and all feeding from seedings to migrations. Every structure is perfectly structured and tailored for a developer to use and libraries. There's no need to use any CDNs, or we can simply install the package and get the specific features. That's a greater part of Laravel PHP Framework.

Laravel PHP Framework enhances our application security posture with various packages and middleware which are available to protect from various kinds of activities.

The most valuable features for building modern web applications in Laravel PHP Framework include the cross-factor authentication, which is handled with middleware. Those things play major roles in providing security before hacking. The route, through which we can categorize and authorize various routes in our web applications and for specific user roles, is also a significant part.

Regarding room for improvement, there are various things at the code level such as Eloquent relationships, including has one and has many, which we can optimize a bit more so that we can get the data faster. If the end developer does not know that, then that's a challenge.

I've been working with Laravel PHP Framework for about four years.

There are no specific challenges we face in Laravel PHP Framework. Everything in Laravel PHP Framework is perfectly tailored.

I have had no performance or limitations with Laravel PHP Framework.

From the maintenance point of view, Laravel PHP Framework is really developer friendly.

There is no maintenance required in Laravel PHP Framework unless the server is high, for instance, if any specific process which we have done custom with a database connection or API calls. In that case, we need to optimize our specific business logic, but there is nothing required from Laravel.

I haven't reached out for Laravel PHP Framework tech support.

Every framework I have worked with, including Laravel PHP Framework, is built on their specific architecture. For instance, Yii is different than Laravel; they are different. Each framework is useful; we cannot find the flaws in them. Ultimately, they provide structured coding practices that we were missing in code when developing core PHP. Instead of just putting a file and running it directly on the web server, with Laravel or CodeIgniter, we can code in a structured manner, which is a beneficial part.

The initial setup of Laravel PHP Framework is straightforward.

The setup process of Laravel PHP Framework requires downloading the latest version of PHP initially and then getting Composer. These are the initial, primary requirements for building a Laravel project. From Composer, we need to start the project by the name using command line code. After that, we can initialize the DB connections in that specific project, if required, then run migrations, generate keys, and for testing, we need to simply run artisan serve. That is the initial phase which is really straightforward to find.

The size of the environment with Laravel PHP Framework currently has about three to four developers working on a single project.

In my project, we usually have three to four developers working with Laravel PHP Framework.

Using Laravel PHP Framework has not impacted my development time or cost in my projects because it's a good best practice which we need to follow on all the complete architecture instead of simply getting a file and putting it directly, which we were doing in normal core PHP.

There are no fees associated with Laravel PHP Framework.

There are various use cases for Laravel PHP Framework, but I don't think there are any disadvantages.

I would recommend Laravel PHP Framework to users or developers using Core PHP; this is the time they need to switch to Laravel, being a decade or more than a decade. Many people are using it. If they are still on Core PHP, then they need to switch.

On a scale of 1 to 10, I rate Laravel PHP Framework as a 10.