The document discusses modern application stacks, emphasizing that there are no one-size-fits-all solutions and challenging the negativity towards traditional LAMP stacks. It highlights the importance of understanding data relationships and application requirements over adopting trends, suggesting practical approaches to selecting servers, databases, and caching methods. The emphasis is on building applications suited for current needs rather than over-engineering for hypothetical large-scale scenarios.

1. Modern Application Stacks Chris Hartjes GTA PHP User's Group May 3, 2011

3. What Are We Going To Talk About NO silver bullets

4. NO group-think

5. NO fixation on the sexy-shiny

6. LAMP is dead LONG LIVE LAMP Why do people hate LAMP so much?

7. PHP Application Stacks Linux

8. Apache

9. MySQL

10. PHP

11. PHP Application Stacks Linux | OS-X | Windows

12. Apache | Nginx | Lighttpd | IIS

13. MySQL | Postgres | SQL Server | Mongo | Couchdb

14. PHP + Javascript

15. The cool kids might say otherwise... LAMP is good enough for YOU Worry about PSS (Precious Snowflake Syndrome)

17. TOY vs. BUSINESS VALUE

18. What is a basic PHP application? Something that accepts a request

19. Something that persists data

20. Some that routes your request

21. Something that displays the response

22. Explosion of PHP Frameworks causes a lack of focus Built for the web

23. Share-nothing

24. 3 rd party integration

25. SOMETHING THAT ACCEPTS YOUR WEB REQUESTS Apache?

26. Lighttpd?

27. Nginx?

28. IIS? IT DOES NOT MATTER

30. Every choice can handle modern needs URL re-writing

31. Ability to pass through dynamic requests

32. Compressing data before serving

33. STFU And Tell Us! Apache – well-understood, easy to get help

34. Nginx + Lighttpd require PHP configuration

35. New tools required for monitoring FCGI

36. Web-server modules are the key

37. Apache + Nginx works too!

38. SOME PERSISTENCE OF DATA NoSQL or RDBMS?

39. Clustered or not-clustered? DEPENDS ON THE DATA

40. Domain model?

41. Heavy reads?

42. Heavy writes?

43. STEP 1: FIGURE OUT RELATIONSHIPS STEP 2: FIGURE OUT USAGE PATTERNS STEP 3: PROFIT?

44. DATA MODEL Key-value?

45. Document?

46. Relational?

47. RDBMS are high-performing and reliable

48. Make great key-value stores (ala Reddit)

49. MySQL will never page you at 3 AM due to obscure replication bug

50. UNSEXY GETS THE JOB DONE

51. http://teddziuba.com/2010/03/i-cant-wait-for-nosql-to-die.html You Are Not Google “ The sooner your company admits this, the sooner you can get down to some real work. Developing the app for Google-sized scale is a waste of your time, plus, there is no way you will get it right. Absolutely none. It's not that you're not smart enough, it's that you do not have the experience to know what problems you will see at scale.”

52. STFU and Tell Us!

53. SOMETHING THAT ROUTES YOUR REQUEST ROUTING IS NOT SEXY

54. SOMETHING THAT ROUTES YOUR REQUEST Frameworks the quickest way

55. Web server rewrite rules for the hardcore

56. Front controller or page controller

57. STFU and Tell Us! System should react to HTTP verbs

58. System should allow reuse of URLs

59. SOMETHING THAT DISPLAYS THE RESPONSE TEMPLATING SYSTEMS ARE NOT SEXY

60. SOMETHING THAT DISPLAYS THE RESPONSE Frameworks the quickest way

61. Designers can learn PHP too!

62. Careful about use of custom tags

63. PHP is a TEMPLATING LANGUAGE

64. STFU And Tell Us! Picking a templating “language” is simply yak shaving

65. STFU And Tell Us! What stack you use actually matters very little

66. Essential Add-ons Alternate PHP Cache (APC) Opcode caching for performance

67. User-space caching

68. Essential Add-ons Memcache In-memory key-value storage

69. Membase (Memcache + persistence)

70. Redis (Memcache compatible)

71. TO THE CLOUD!

74. What Orchestra Offers “The idea is that we aren't the dated LAMP stack but rather a more modern nginx, load-balanced, caching, php-fpm, mongo, etc.” “A platform built for today and tomorrows needs instead of a traditional platform made to handle the problems we had 10-15 years ago.”

75. Now Architecture Matters Performance different

76. Count on components disappearing

77. Application architecture matters!

79. THANK YOU Questions?

80. Comments?

81. Complaints http://www.littlehart.net/atthekeyboard