CodeIgniter is a free and open source PHP framework, developed originally by EllisLab.
N/A
Laravel PHP Framework
Score 8.7 out of 10
N/A
Laravel is a free, open source web application PHP framework.
N/A
Pricing
CodeIgniter
Laravel PHP Framework
Editions & Modules
No answers on this topic
No answers on this topic
Offerings
Pricing Offerings
CodeIgniter
Laravel PHP Framework
Free Trial
No
No
Free/Freemium Version
No
No
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
No setup fee
No setup fee
Additional Details
—
—
More Pricing Information
Community Pulse
CodeIgniter
Laravel PHP Framework
Considered Both Products
CodeIgniter
Verified User
Director
Chose CodeIgniter
CodeIgniter is a lot easier to implement than Laravel. Even though laravel has a lot of other features, they weren't really important for me. I cared about fast deployment and product release and CodeIgniter helped me do it perfectly.
CodeIgniter has a very small footprint. The source code is very small sized. Setting up a project is very easy. Follows MVC pattern. Consumes low memory and CPU. Well documented. Has a built-in forum for users to discuss and get the solution for issues. Periodically updates …
Because of CodeIgniter's fast speed and well-developed architecture, it stacks up against the rest of the PHP frameworks. CodeIgniter can also be modified to use the Hierarchical Model View Controller (HMVC) development pattern which allows CodeIgniter developers to group …
Codeigniter's syntax patterns are expressive and elegant. Unit testing support. Well documented. but as CodeIgniter tries to retain backward compatibility with PHP 4, here comes Laravel to the rescue. It has good features and it is updated. Wikipedia has mentioned, “according …
Although lacks installation using composer, its not difficult to install this framework. Because of its open platform, documentation and resources its easy to create a project and make it better. Can get a lot of help from the developer community who have used it previously. …
Laravel is the de facto upgrade path for any and all web developers coming from any version of CodeIgniter. However, Laravel brings a level of complexity that can be intimidating to new developers or wasteful to experienced developers with simple requirements.
CodeIgniter is a great choice for small or medium projects that can be deployed in every kind of hosting, especially those oriented to low-cost hostings like GoDaddy. Symfony and Laravel are frameworks for highly scalable projects with hundreds of plugins available. Also, these …
Both older and new versions of CodeIgniter lack installation via Composer. Laravel is our other framework of choice; its installation, updates, and addition of third party packages are significantly easier with Composer. CodeIgniter is our primary framework as our CMS is build …
When we were using CodeIgniter, it always felt that something is missing. We were unable to find the proper libraries that supports it and the support from the community around. Once we came to know about Laravel, we never have touched CodeIgniter. Laravel is a well documented …
Verified User
Engineer
Chose Laravel PHP Framework
If you are using PHP, you should be using Laravel! It is superior in every way to CodeIgniter & CakePHP. Not to be unfair to Cake & CodeIgniter, which both have built in ORM, making queries very simple. Laravel on the other hand offers their eloquent ORM that makes database …
Originally, it was a decision between Zend, CodeIgniter, and CakePHP for me. I chose CakePHP and used it as my main PHP framework for at least a couple of years before noticing and giving Laravel a fair try. Ultimately I selected Laravel because I felt it fit with my preferred …
Laravel is much better than CodeIgniter in many aspects, First of all it is more secure and robust. It has a great troubleshooting mechanism. They have added more libraries, themes and plug-ins for different purposes. The MVC model helped the developers to get rid of writing …
I have used CodeIgniter in the past for a couple of projects. As per my experience, we can go for CodeIgniter for smaller projects due to its simplicity. But as the project size grows, one should choose a more organized framework with larger community support. This is the …
The majority of the above-mentioned frameworks are good at some particular things. Laravel PHP Framework in general is capable of doing all the same things with standard best practices. Additionally, Laravel PHP Framework brings great community support that is ever-growing. the …
Laravel PHP Framework is the most developed, updated framework right now, with lots of features. Using older versions is less appreciated by the developer community. It is well documented, and Laravel has a pretty big community of supporters getting your query solved faster and …
Supporting unit testing is bigger plus point in Laravel than any other framework. Developing with Laravel is much easier. Other frameworks have value in market, but Laravel has taken the lead in popularity among PHP developers in recent years. The large community supports you …
Laravel PHP Framework is continuously updating its framework and developing new tools to make web development more useful, optimized, and bug-free. Also there is a large community of users on Stack Overflow and other websites that can help you get questions cleared up quickly. …
Laravel is built on top of Symfony so is naturally a better upgrade. It is far superior than cake and igniter (in my opinion). I don't remember, but somewhere in internet someone made a comparison with Laravel and others as racing motor-bike vs a cycle. Because of large …
The best comparison I can make is against Symfony. It's curious that Laravel is built on top of Symfony. They chose the packages that they found to be useful. Symfony for instance comes with way too much stuff that in the end you never use, and Laravel just comes with the right …
The input class makes it easy to provide server-side validation and scrubbing of user input. Setting Error messages. It doesn't require constant command-line access, It's great because it has a strong community and excellent documentation, but the problem is that it tries to retain backward compatibility with PHP 4 and therefore lacks a lot of "standard" features modern frameworks have such as auto-loading.
Laravel is ideally suited for fluent PHP developers who want a framework that can be used to both rapidly prototype web applications as well as support scalable, enterprise-level solutions. I think where it is less ideal is where the client has an expectation of using a certain CMS, or of having a certain experience on the admin side that would perhaps be better suited to a full CMS such as Drupal or WordPress. Additionally, for developers who don't want to write PHP code, Laravel may not be the best solution.
CodeIgniter is an excellent tool when a simple database API is needed. Postgres, MySQL, and SQLite are all abstracted into a simple-to-use
CodeIgniter's simplicity is truly its best feature, because you are able to create controllers and methods based on the http://www.example//, and immediately being developing the application.
Flexibility is also another developer-friendly feature, because developers are able to design their application in any way - controllers, models, libraries, and helpers can be located anywhere or not used at all.
Faced some issue of session management, so that's why we used the Core Session library for that. It would be great if we could improve it a little bit.
Frameworks provide the option to setup all getters/setters, so having this option in it is a great idea.
Significant learning curve. You cannot be an expert in a week. It takes many experimentations to properly understand the underlying concept. We ourselves learned it by using it on the job.
Too much to soak in. Laravel is in everything. Any part of backend development you wish to do, Laravel has a way to do that. It is great, but also overwhelming at the same time.
Vendor lock in. Once you are in Laravel, it would not be easy to switch to something else.
Laracasts (their online video tutorials) are paid :( I understand the logic behind it, but I secretly wish it would be free.
The eloquent ORM is not my recommendation. Let's say you want to write a join, and based on the result you wish to create two objects. If you use Laravel to do automatic joins for you, Laravel internally actually makes two calls to database and creates your two object rather than making one join call and figuring out the results. This makes your queries slow. For this reason, I use everything except eloquent from Laravel. I rather write my own native queries and control the creation of objects then rely on Laravel to do it. But I am sure with time Laravel will make fewer calls to DB.
CodeIgniter has a very small footprint. The source code is very small sized. Setting up a project is very easy. Follows MVC pattern. Consumes low memory and CPU. Well documented. Has a built-in forum for users to discuss and get the solution for issues. Periodically updates versions and patch fixes etc.
Supporting unit testing is bigger plus point in Laravel than any other framework. Developing with Laravel is much easier. Other frameworks have value in market, but Laravel has taken the lead in popularity among PHP developers in recent years. The large community supports you if you have problems. Using Laravel, integration became easy with third-party libraries, but it was costly too.
Laravel allows us to rapidly prototype and build complete, scalable applications internally, which saves us time and allows us to have internal tools that fit out precise needs. We use Symfony for a similar purpose, but Laravel is an even higher-level framework that we find saves us substantially more time when building many types of web applications.
Laravel solves many of the underlying concerns of building a large application (such as authentication, authorization, secure input handling) in the right ways. It saves us from handling those low-level concerns ourselves, potentially in a way that could take a lot of time or sets us up for issues in the future. It's tough to assign an ROI to this, but I'm sure it has prevented issues and saved time, which both have an impact on our financial situation.