From Wikipedia, the free encyclopedia
Jump to: navigation, search
Laravel logo
Developer(s) Taylor Otwell
Initial release June 2011; 4 years ago (2011-06)[1]
Stable release 5.1.19[2] / October 1, 2015; 8 days ago (2015-10-01)
Development status Active
Written in PHP 5[a]
Operating system Cross-platform
Type Web application framework
License MIT License

Laravel is a free, open-source PHP web application framework, created by Taylor Otwell and intended for the development of web applications following the model–view–controller (MVC) architectural pattern. Some of the features of Laravel are a modular packaging system with a dedicated dependency manager, different ways for accessing relational databases, utilities that aid in application deployment and maintenance, and its orientation toward syntactic sugar.[4][5]:2,5–9[6][7]

As of March 2015, Laravel is regarded as one of the most popular PHP frameworks, together with Symfony2, Nette, CodeIgniter, Yii2 and other frameworks.[5]:1[8]

The source code of Laravel is hosted on GitHub and licensed under the terms of MIT License.[9]


Taylor Otwell created Laravel as an attempt to provide a more advanced alternative to the CodeIgniter framework, which did not provide certain features such as built-in support for user authentication and authorization. Laravel's first beta release was made available on June 9, 2011, followed by the Laravel 1 release later in the same month. Laravel 1 includes built-in support for authentication, localisation, models, views, sessions, routing and other mechanisms, but lacks support for controllers that prevents it from being a true MVC framework.[1]

Laravel 2 was released in September 2011, bringing various improvements from the author and community. Major new features include the support for controllers, which made Laravel 2 a fully MVC-compliant framework, built-in support for the inversion of control (IoC) principle, and a templating system called Blade. As a downside, support for third-party packages was removed in Laravel 2.[1]

Laravel 3 was released in February 2012 with a set of new features including the command-line interface (CLI) named Artisan, built-in support for more database management systems, database migrations as a form of version control for database layouts, support for handling events, and a packaging system called Bundles. An increase of the Laravel's userbase and popularity lined up with the release of Laravel 3.[1]

Laravel 4, codenamed Illuminate, was released in May 2013. It was made as a complete rewrite of the Laravel framework, migrating its layout into a set of separate packages distributed through Composer, which serves as an application-level package manager. Such a layout improved the extendibility of Laravel 4, which was paired with its official regular release schedule spanning six months between minor point releases. Other new features in the Laravel 4 release include database seeding for the initial population of databases, support for message queues, built-in support for sending different types of email, and support for delayed deletion of database records called soft deletion.[1][10]:18–19

Laravel 5 was released in February 2015 as a result of internal changes that ended up in renumbering the then-future Laravel 4.3 release. New features in the Laravel 5 release include support for scheduling periodically executed tasks through a package called Scheduler, an abstraction layer called Flysystem that allows remote storage to be used in the same way as local file systems, improved handling of package assets through Elixir, and simplified externally handled authentication through the optional Socialite package. Laravel 5 also introduced a new internal directory tree structure for developed applications.[5]:13–14[11]

Laravel 5.1, released in June 2015, is the first release of Laravel to receive long-term support (LTS), with planned availability of bug fixes for two years and security patches for three years. LTS releases of Laravel are planned to be released every two years.[12]


The following features serve as Laravel's key design points (where not specifically noted, descriptions refer to the features of Laravel 3):[4][5]:5–9[6][7][13]

  • Bundles provide a modular packaging system since the release of Laravel 3, with bundled features already available for easy addition to applications. Furthermore, Laravel 4 uses Composer as a dependency manager to add framework-agnostic and Laravel-specific PHP packages available from the Packagist repository.[14]
  • Eloquent ORM (object-relational mapping) is an advanced PHP implementation of the active record pattern, providing at the same time internal methods for enforcing constraints on the relationships between database objects. Following the active record pattern, Eloquent ORM presents database tables as classes, with their object instances tied to single table rows.[15][16]
  • Query builder, available since Laravel 4, provides a more direct database access alternative to the Eloquent ORM. Instead of requiring SQL queries to be written directly, Laravel's query builder provides a set of classes and methods capable of building queries programmatically. It also allows selectable caching of the results of executed queries.[17]
  • Application logic is an integral part of developed applications, implemented either by using controllers or as part of the route declarations. The syntax used to define application logic is similar to the one used by Sinatra framework.
  • Reverse routing defines a relationship between the links and routes, making it possible for later changes to routes to be automatically propagated into relevant links. When the links are created by using names of existing routes, the appropriate uniform resource identifiers (URIs) are automatically created by Laravel.
  • Restful controllers provide an optional way for separating the logic behind serving HTTP GET and POST requests.
  • Class auto loading provides automated loading of PHP classes without the need for manual maintenance of inclusion paths. On-demand loading prevents inclusion of unnecessary components, so only the actually used components are loaded.
  • View composers serve as customizable logical code units that can be executed when a view is loaded.
  • Blade templating engine combines one or more templates with a data model to produce resulting views, doing that by transpiling the templates into cached PHP code for improved performance. Blade also provides a set of its own control structures such as conditional statements and loops, which are internally mapped to their PHP counterparts. Furthermore, Laravel services may be called from Blade templates, and the templating engine itself can be extended with custom directives.[18][19]
  • IoC containers make it possible for new objects to be generated by following the inversion of control (IoC) principle, in which the framework calls into the application- or task-specific code, with optional instantiating and referencing of new objects as singletons.
  • Migrations provide a version control system for database schemas, making it possible to associate changes in the application's codebase and required changes in the database layout. As a result, this feature simplifies the deployment and updating of Laravel-based applications.[20]
  • Database seeding provides a way to populate database tables with selected default data that can be used for application testing or be performed as part of the initial application setup.[20]
  • Unit testing is provided as an integral part of Laravel,[10]:61–62 which itself contains unit tests that detect and prevent regressions in the framework. Unit tests can be run through the provided artisan command-line utility.
  • Automatic pagination simplifies the task of implementing pagination, replacing the usual manual implementation approaches with automated methods integrated into Laravel.
  • Form request is a feature of Laravel 5 that serves as the base for form input validation by internally binding event listeners, resulting in automated invoking of the form validation methods and generation of the actual form.[21]

Featured packages[edit]

Ready-to-use bundles provided by Laravel through Composer and Packagist include the following:[3]

  • Cashier, introduced in Laravel 4.2, provides an interface for managing subscription billing services provided by Stripe, such as handling coupons and generating invoices.
  • SSH, introduced in Laravel 4.1, allows programmatic execution of CLI commands on remote servers using the Secure Shell (SSH) as an encrypted network protocol.
  • Scheduler, introduced in Laravel 5.0, is an addition to the Artisan that allows programmatic scheduling of periodically executed tasks. Internally, Scheduler relies on the cron daemon to run a single Artisan job that, in turn, executes the configured tasks.
  • Flysystem, introduced in Laravel 5.0, is a file system abstraction layer that allows local file systems and cloud-based storage services provided by Amazon S3 and Rackspace Cloud to be used transparently and in the same way.
  • Socialite, introduced in Laravel 5.0 as an optional package, provides simplified mechanisms for authentication with different OAuth providers, including Facebook, Twitter, Google, GitHub and Bitbucket.[5]:13

Artisan CLI[edit]

Laravel's command-line interface (CLI), called Artisan, was initially introduced in Laravel 3 with a limited set of capabilities. Laravel's later migration to a Composer-based architecture allowed Artisan to incorporate different components from the Symfony framework, resulting in the availability of additional Artisan features in Laravel 4.[10]:73–83[22]

The features of Artisan are mapped to different subcommands of the artisan command-line utility, providing functionality that aids in managing and building Laravel-based applications. Common uses of Artisan include managing database migrations and seeding, publishing package assets, and generating boilerplate code for new controllers and migrations; the latter frees the developer from creating proper code skeletons. The functionality and capabilities of Artisan can also be expanded by implementing new custom commands, which, for example, may be used to automate application-specific recurring tasks.[10]:73–83[22]


Laracon is a conference centered around the Laravel framework, covering its development, uses, and related general software development practices. Laracons are taking place in both United States and Europe, organized primarily by UserScape with additional help provided by a number of sponsors.[23] As of July 2015, the following Laracons have been held or are announced:[24]

Date Location
February 22–23, 2013 Washington, D.C.
August 30–31, 2013[25] Amsterdam
May 15–16, 2014 New York City
August 28–30, 2014[26] Amsterdam
August 11–12, 2015[27] Louisville, Kentucky
August 25–26, 2015[28] Amsterdam

See also[edit]


  1. ^ PHP version 5.3.7 or newer is required for Laravel versions 4.1 and older, Laravel 4.2 and 5.0 require at least PHP 5.4, while Laravel 5.1 requires PHP 5.5.9 or newer.[3]


  1. ^ a b c d e Maks Surguy (July 27, 2013). "History of Laravel PHP framework, Eloquence emerging". Retrieved May 10, 2015. 
  2. ^ "laravel/framework: Release v5.1.19". October 1, 2015. Retrieved October 8, 2015. 
  3. ^ a b "Laravel documentation (version 5.1): Release notes". Retrieved June 14, 2015. 
  4. ^ a b Daniel Gafitescu (June 6, 2013). "Goodbye CodeIgniter, Hello Laravel". Retrieved December 21, 2013. 
  5. ^ a b c d e Martin Bean (April 2015). Laravel 5 Essentials. (Packt). ISBN 978-1785283017. Retrieved September 2, 2015. 
  6. ^ a b "Laravel Documentation (versions 3.0–3.2.14)". Retrieved August 30, 2014. 
  7. ^ a b "Laravel Documentation (version 4.2)". Retrieved August 30, 2014. 
  8. ^ Bruno Skvorc (March 28, 2015). "Best PHP Framework for 2015 – SitePoint Survey Results". Retrieved June 14, 2015. 
  9. ^ "laravel/laravel: laravel/ at master". April 22, 2015. Retrieved May 10, 2015. 
  10. ^ a b c d Raphaël Saunier (January 2014). Getting Started with Laravel 4. (Packt). ISBN 978-1783287031. Retrieved September 2, 2015. 
  11. ^ Eric Barnes (January 30, 2015). "Laravel 5". Retrieved May 10, 2015. 
  12. ^ Eric L. Barnes (June 9, 2015). "Laravel 5.1 is released". Retrieved June 14, 2015. 
  13. ^ Jeffrey Way (November 28, 2012). "Why Laravel is Taking the PHP Community by Storm". Retrieved May 9, 2015. 
  14. ^ "Laravel documentation (version 4.2): Package development". Retrieved August 30, 2014. 
  15. ^ "Eloquent ORM in Laravel: What and Why!". Retrieved December 19, 2014. 
  16. ^ "Develop Faster with the Laravel PHP Framework". Retrieved April 17, 2015. 
  17. ^ "Laravel documentation (version 4.0): Query builder". Retrieved April 27, 2015. 
  18. ^ "Laravel documentation (version 5.1): Blade Templates". Retrieved June 10, 2015. 
  19. ^ Dayle Rees (2014). "Laravel Blade engine". Retrieved June 10, 2015. 
  20. ^ a b "Laravel documentation (version 5.0): Migrations and seeding". Retrieved April 27, 2015. 
  21. ^ Manmeet Anand. "Creating a Contact Form in Laravel 5 Using the Form Request Feature!". Retrieved March 2, 2015. 
  22. ^ a b Jason Lewis (February 28, 2013). "Your One-Stop Guide to Laravel Commands". Retrieved May 9, 2015. 
  23. ^ "Userscape home page". Retrieved January 2, 2014. 
  24. ^ "Laravel documentation: Laracon". Retrieved January 2, 2014. 
  25. ^ "Laracon EU 2013". Retrieved January 2, 2014. 
  26. ^ "Laracon EU 2014". Retrieved August 30, 2014. 
  27. ^ "Laracon 2015 will be in Louisville KY". January 15, 2015. Retrieved July 9, 2015. 
  28. ^ "Laracon EU 2015". Retrieved July 9, 2015. 

Further reading[edit]

External links[edit]