Software design patterns in laravel by phill sparks

1. Software Design Patterns
in Laravel 4
by Phill Sparks

2. Credits
• Rosalind Goodall - Graphics
• Taylor Otwell - Laravel

3. @PhillSparks

4. @PhillSparks
• API Engineer at CrowdLab

5. @PhillSparks
• API Engineer at CrowdLab
• From Leicester, UK

6. @PhillSparks
• API Engineer at CrowdLab
• From Leicester, UK
• Climbing Instructor

7. @PhillSparks
• API Engineer at CrowdLab
• From Leicester, UK
• Climbing Instructor
• Scout

8. @PhillSparks
• API Engineer at CrowdLab
• From Leicester, UK
• Climbing Instructor
• Scout
• Laravel Core Team

9. Laravel
• With Laravel since 1.5.9
• Core Team Member
• Past: Quality Team
• Now: Community engagement and support

10. Laravel
• With Laravel since 1.5.9
• Core Team Member
• Past: Quality Team
• Now: Community engagement and support
• Dayle still owes me 9000 support points!

11. Software Design Patterns
“ ”
Each pattern describes a problem which occurs over
and over again in our environment, and then describes
the core of the solution to that problem, in such a
way that you can use this solution a million times
over, without ever doing it the same way twice.
-- Christopher Alexander, AIS+77

12. Software Design Patterns

13. Software Design Patterns

14. The Patterns
• Builder
• Chain of Responsibility
• Command
• Facade
• Factory
• Iterator
• Mediator
• Observer
• Presenter
• Repository
• Singleton
• Strategy

15. Notations

16. Class
Notations

17. Sub-class
Notations

18. Abstract Class
Notations

19. Class Instance
Notations

20. Implementation
Notations

21. Building Blocks

22. Interfaces
namespace IlluminateAuth;
interface UserInterface {
public function getAuthIdentifier();
public function getAuthPassword();
}
class GenericUser implements UserInterface {

23. Interface
• 244 interfaces in Laravel (including vendors)
• 25 from Laravel Core
• 65 from Symfony
• 73 from Swiftmailer

24. Abstract Classes
namespace IlluminateDatabaseEloquentRelations;
abstract class Relation {
abstract public function addConstraints();
abstract public function getResults();
}
class BelongsTo extends Relation {

25. Abstract Classes
• 128 abstract classes in Laravel (including
vendors)
• 14 from Laravel Core
• 15 from Swiftmailer
• 40 from Symfony

26. Iterator

27. PHP’s Iterator Interface

28. Laravel’s Iterators
• Collection
• Paginator

29. Observer

30. namespace IlluminateEvents;
Dispatcher

31. namespace IlluminateEvents;
Dispatcher
class LoginHandler {
function handle($user) {
// do something with $data
}
}
Event::listen(‘user.login’, ‘LoginHandler’);
Event::fire(‘user.login’, $user);

32. Singleton

33. namespace IlluminateFoundation;
AliasLoader

34. Multiton

35. namespace IlluminateDatabase;
DatabaseManager

36. Facade

37. namespace IlluminateSupportFacades;
Facade

38. namespace IlluminateSupportFacades;
Input

39. namespace IlluminateSupportFacades;
Route

40. namespace IlluminateSupportFacades;
Response

41. namespace IlluminateSupport;
Str

42. Facade vs Singleton

43. Decorator

44. namespace IlluminatePagination;
BootstrapPresenter

45. namespace IlluminatePagination;
BootstrapPresenter

46. Repository
• Examples:
• IlluminateCacheRepository
• IlluminateConfigRepository

47. Builder (aka Manager)
• Examples:
• IlluminateAuthAuthManager
• IlluminateCacheCacheManager
• IlluminateQueueQueueManager
• IlluminateSessionSessionManager

48. Factory
• Examples:
• IlluminateDatabaseDatabaseManager
• IlluminateDatabaseConnectors
ConnectionFactory
• IlluminateValidationFactory

49. Service Provider
• Core to Laravel’s IoC
• See IlluminateSupportServiceProvider
• Examples:
• IlluminateAuthAuthServiceProvider
• IlluminateHashHashServiceProvider
• IlluminateLogLogServiceProvider

50. Strategy
• Examples:
• IlluminateCacheStoreInterface
• IlluminateConfigLoaderInterface
• IlluminateDatabase - Builders & Grammars
• IlluminateTranslationLoaderInterface
• IlluminateViewViewFinderInterface

51. s/PhillSparks//