This document discusses models in PHP applications. It begins by defining a model as a logical representation of data. Models have three main components: the thing being modeled, where the data is stored, and how to interact with the data. The document then provides tips for designing models such as starting with the question of what is being modeled and modeling items that can stand alone individually. Finally, it outlines what parts of an application belong in a model, such as data storage logic, versus parts that do not, like display logic.

1. Beautiful Models In PHP
By Brandon Savage

2. Do your models look like this?

3. You never wanted your
code to look this way.
Let’s fix it.

4. Who am I?
• Software engineer at
Mozilla.
• Blogger, speaker, author
of Mastering Object
Oriented PHP
• Instrument rated private
pilot.

5. Questions we’ll answer
1.What is a model?
2.What are the components of a model?
3.How do you design a model?
4.What parts of an app belong in a model?
5.What parts of an app do not belong in a
model?
(last bullet slide I swear!)

6. What is a model?

7. (Conceptual) Model - a method for
representing ‘concepts’ (entities) and the
relationship between them. (Wikipedia)

8. A model is a method of
representing data in a
logical way.

9. Friends
Blog posts
Customers
News stories
Sermons Users
Clients
Political parties
Transactions
Television shows
Comments
Lovers

10. Sometimes models map directly to
a database table.
A lot of times they don’t.

11. Models != Database
Tables

12. In fact, models may not
have databases at all.

13. MySQL/PostgreSQL
REST APIs
Amazon
Redis
Elastic Search
Memcache
APC MongoDB
File system
Web services
Other web apps

14. What are the
components of a model?

15. 1. The thing you’re
modeling.

16. Friends
Blog posts
Customers
News stories
Sermons Users
Clients
Political parties
Transactions
Television shows
Comments
Lovers

17. 2. The place the data is
stored.

18. MySQL/PostgreSQL
REST APIs
Amazon
Redis
Elastic Search
Memcache
APC MongoDB
File system
Web services
Other web apps

19. 3. The method for
interacting with these
two items.

20. Domain modeling

21. Single responsibility
principle

22. How do you design a
model?

23. Start with a question:
what am I modeling?

24. Bank customers have
accounts.
They also have phone
numbers.

26. <?php
class Customer { ... }
<?php
class PhoneNumber { ... }
<?php
class Account { ... }

27. <?php
class Customer {
protected $phone_numbers = array();
protected $accounts = array();
public function get_phone_numbers() { ... }
}
<?php
class Account {
protected $customer;
}

28. Each value object is
populated by the
gateway object.

29. Items that can be
modeled individually
should be.

30. Items that are too small
to model individually
shouldn’t be.

31. What parts of an app
belong in a model?

32. Data storage and
retrieval operations

33. Business logic

34. Validation logic

35. What parts of an app
do not belong in a
model?

36. Display logic

37. Object creation

38. Data passing and
collection

39. Want to learn more?
Stop struggling with
object oriented PHP.
Start mastering it
instead.
DC PHP members get 10% off!
Use DCPHP10 at checkout.
www.masteringobjectorientedphp.com

40. The Object Oriented
PHP Masterclass
Get hands on experience using what you just learned.
Coming in March. Seats are limited!
Sign up for updates at brandonsavage.net

41. Questions?
• Email: brandon@brandonsavage.net
• Twitter: @brandonsavage
• Website: http://www.brandonsavage.net