This document discusses PHP as an open-source alternative for enterprise development. It provides an overview of PHP and its advantages, including being easy to learn, flexible, platform independent, and having a large community and libraries. It also discusses best practices for PHP development, such as using frameworks, testing, security, performance, and tools.

1. Professional PHP an open-source alternative for enterprise development Thijs Feryn Felix De Vliegher 28/11/’08, KDG Antwerpen

3. PHP developer for about 5 years

4. Zend PHP5, certified engineer

6. PHP developer for about 7 years

7. Zend PHP5, Zend Framework certified engineer

8. Co-founder PHPBelgium

9. Contributor to the PHP project and Zend Framework

11. 30 FTE and growing

12. +25 000 customers

13. Premium / Quality hosting segment

15. + 20 000 websites

16. + 600 servers, owned & managed by COMBELL

17. + 400 resellers

19. Experience with PHP

20. Experience with PHP based applications

21. OOP in PHP?

22. Professional experience? (non-academic)

24. Source code is available

25. Use, change, improve

26. Collaborative

27. Common licenses: GPL, LGPL, MIT

28. Free “as in beer”

30. Linux, Apache, MySQL and PHP

31. Open-source, free software

32. Available everywhere

33. Proven track record Application PHP Apache MySQL Linux

34. Why PHP? Easy to learn

36. Platform independent

37. Lots of libraries, frameworks

38. Huge community

39. Code is freely available

40. Documentation

41. Commercial support

42. Short TTM

44. Low entry barrier

45. Stateless

46. Platform independence (vs .NET)

47. Interpreted language

49. Pecl

50. Pear (let’s say Java?)

51. PHP is community friendly

53. Initiatives to contribute and learn

55. irc

56. twitter

57. Shiny statistics (sort of) PHP 4 Yahoo goes PHP PHP 5 IBM & Oracle endorse PHP Microsoft endorses PHP PHP 6?

58. PHP Applications

59. Used by

60. COMBELL customers using PHP

61. Support by

62. PHP in the enterprise Evolution from a functional approach to enterprise fundamentals

63. The fundamentals

65. Often the first and only concern

67. Testing & debugging

69. More structure

70. Glue (component) vs full-stack

71. DRY

72. No maintenance

73. Extend or plugin where needed

76. Security 1: Thou shalt filter input and escape output

79. Databases

80. Sessions

83. No premature optimization!

86. Indexing strategy

87. Writing good SQL

89. Optimalization of PHP as a language

91. Design patterns - MVC

92. Database scaling - sharding

93. Development methodologies - agile, scrum

94. Version control

95. Documentation!

96. Testing I pity the fool who doesn’t write tests!

98. Applications should work as expected

99. Actually takes less time

100. Provides higher quality

101. Easier to refactor and change

102. Makes confident developers

103. Testing and coverage

106. Selenium - http://selenium.seleniumhq.org

108. Zend Framework Certification

110. Get listed in Zend Yellow Pages

111. Confirmation of a decent PHP skillset

113. For developers, education, businesses

114. Bi-monthly meetings ( http://www.phpbelgium.be )

116. PHP Bug Hunt Day ( http://www.bughuntday.org )

118. Power PHP 5 programming

122. Highly integrated with hosted solutions

123. Using Zend Framework, Symfony

125. Unit testing

126. Continuous integration (Cruisecontrol)

129. Valid career choice, not everything needs to be done with Java or .NET

130. PHP Engineers are in high demand!

131. If our presentation were a book

132. Thanks! Any questions? More info: [email_address] [email_address]