The document discusses different approaches for organizing and structuring code for a web application and breaking a web application into multiple programs that communicate with each other. It begins with basic approaches like putting all code in one file or splitting into classes and files based on functionality. It then discusses more advanced approaches like using a database, cache, message queues, or remote procedure calls as the coordination point between components and how to structure applications using those approaches. It concludes by noting some additional challenges in web development like monitoring, deployment, and data management that weren't covered.

1. How do you, like,
split your web site up?
You know what I mean?
A tech talk at Paperless Post
by Alex Payne
November 2012

5. Beginner:
How do you organize the
code for your site?

6. site.php

7. site.php
class Page {}
class Login extends Page {}
...

8. site.php db.php

9. site.php db.php
helpers.php

10. Model View Controller
person.php login.php auth.php

12. Advancing:
How do you break a web
application into multiple
programs? How do they
talk to one another?

13. dat_app

14. dat_app

15. Database
as point of coordination
nightly.rb
dat_app

16. Databasestore
as point of coordination
nightly.rb
dat_app

17. Cache
as point of coordination
dat_app
hourly.rb

18. Message Queues
dat_app
worker1
worker2

19. RPC
via native serialization
chat
DRb dat_app
worker1
search
worker2

20. RPC
via JSON
chat
dat_app
worker1
search
worker2

21. RPC
pro-style
chat
dat_app
worker1
search
worker2

22. «pause»

23. chat
site.php
search

24. WE STILL HAVEN'T
TALKED ABOUT:
‣ Monitoring
‣ Multi-datacenter support
‣ Service discovery
‣ Deployment
‣ Schema migrations
‣ Analytics/data mining
‣ ....

25. 1. Web development isn't
inherently difficult, but it
gets really challenging
really quickly.

26. 2. This is why the future
belongs to PaaS.

27. Thanks!