Here I speak about how you can quickly spin up a Laravel application and related topic such as Design Principles, Best practices, TDD and many more. Take a look and share you thoughts. Cheers!

1. Evolve with Laravel
-Gayan Sanjeewa

2. What you’ll learn:
● Must know features and components.
● Standards and recommendations.
● Initialize an app from fresh.
● Glimpse of unit testing.

3. Choose your ground.

4. Choose your ground.
● Why Laravel? what the community says
○ https://laravel-news.com/2016-survey
● Is it perform well? let's ask from Taylor Otwell
○ https://medium.com/@taylorotwell/benchmarking-laravel-symfony-zend-2c01c2b270f8
● RAD
● Small to mid to enterprise level
● Lumen for Micro-services

5. Choose your ground.
● Env
○ Lamp/Homestead/Valet/Docker
● Editor
○ Phpstorm/sublime
○ Postman for api testing

6. Install

7. Install
● Latest version is Laravel 5.4
● Laravel 5.5 is going to be the new LTS version, which is in final stage of
development.
● Install Using Laravel Installer
○ composer global require "laravel/installer"
○ laravel new --dev api.acme
● Install Via composer create-project
○ composer create-project laravel/laravel api.acme dev-develop

8. Structure
● Artisan - laravel cli
● .env vs .env.example
● .gitignore
● composer.json Vs composer.lock
● composer install Vs composer update
● public/Index.php
● config/app.php
● http/Kernal.php & console/Kernal.php
● phpunit.yml
● storage/log/laravel.log
● Use git right from start!
● Always use PSR! (http://www.php-fig.org/psr)

9. PSR?

10. PSR?
● There's only two types of programmers.
● PSR recommends the second type ;)
● Set Up in phpstorm

11. TDD?

12. TDD?

13. TDD process

14. Let build an App

15. Scope,
"In Acme Corp,
a user can create many products.
A product can have many tags and vise versa.
When the product is created, a confirmation email should be
sent to the user."

16. Demo project
Download from
https://github.com/gayansanjeewa/api.acme.git

17. Convention Over Configuration
● Introduced by David Heinemeier Hansson
to describe the philosophy of the Ruby on
Rails web framework.
● Applies to any framework.
● Ex: If there is a class “Category” in the
model, the corresponding table in the
database is called "categories" by default.
● It is only if one deviates from this
convention, such as the table
"product_categories", that one needs to
write code regarding these names.

18. Database
● Table name: plural, snake_case
○ Users
○ products
○ tags
● Column name: singular, snake_case
○ email
○ product_id
● Pivot table name: singular, snake_case, alphabetically
ordered
○ product_tag
○ post_user

19. ● In Route/Controller/Model or use Repository/Service or use Module?
● Why Migration and seeds needed?
● How to validate requests?
● Why Event-Listeners and when to use domain events.
● How to trigger Email properly?
● Why and when middleware
○ Ex: trim, null string. Auth
● Keep things SOLID!
Where should my code go?

20. We’ll also look at,
● Eloquent
● Collections
● Builder
● Eager loading - Products per users
● $user->products() vs $user->products
● Facade
● Jwt
● cache, queue, cron, command

21. Q&A

22. Rest is up
to you!

23. Thanks!