TYPO3 can be scaled to support high traffic websites through techniques like: 1) Vertical scaling of individual servers by optimizing code and adding resources like RAM and CPUs 2) Horizontal scaling by adding more application and database servers and using load balancers to distribute traffic 3) Caching dynamic content, database queries, and files to reduce load on application and database servers

1. TYPO3 Scalability for high traffic Websites Presenter: Dan Osipov http://danosipov.com Twitter: @danosipov

2. About me Work with TYPO3 full time since 2007 Used TYPO3 for high traffic dynamic news sites DAM Team leader Author of TYPO3 4.3 Multimedia Cookbook from Packt

3. What is Scalability? “Desirable property of a system which indicates its ability to either handle growing amounts of work in a graceful manner or to be readily enlarged.”[1] [1] http://en.wikipedia.org/wiki/Scalability

4. Why scale? Support more traffic Offer better response time High availability & minimum downtime

5. Vertical scaling

6. Vertical scaling

7. Vertical scaling

8. Horizontal scaling

9. How to build a scalable system? Develop benchmarks Optimize the site Find bottlenecks Experiment Art more than a science

10. Benchmarking Benchmarks: measurable goals you can use to track progress ab Jmeter Profiling Monitoring

11. Caching Cache everything that can be cached TYPO3 Cache Use different backends (TYPO3 >4.3) MySQL Query Cache PHP Bytecode cache eaccelerator APC X-Cache

12. Separating Processing & DB

13. Separating Processing & DB Point TYPO3 to a different host for DB Optimize servers for their function Multiple processors for processing server Fast disks and RAM for DB server Compress data between processing & DB server $TYPO3_CONF_VARS['SYS']['dbClientCompress']

14. Scaling application servers

15. Scaling application servers Load balancer Round robin DNS Hardware load balancer Software load balancer (nginx) Centralize storage Fileadmin on NFS rsync

16. Scaling application servers

17. Scaling DB servers

18. Scaling DB servers Sharding Master-Slave Replication Easy to set up for most DB systems t3p_scalable Read (SELECT) requests go to slave servers Write (INSERT, UPDATE, DELETE, etc) requests go to the master

19. Scaling DB servers

20. Scaling File System

21. Scaling File System Amazon S3 cdnfiles Replaces “fileadmin/”, “uploads/”, “typo3temp/pics/” links to CDN equivalents Isn’t responsible for uploading or maintaining CDN versions

22. High Availability

23. High Availability

24. High Availability

25. Limitations Single Master DB Every FE request requires a connection to the master 100% availability (failover in catastrophic cases) Difficult to scale

26. Cloud computing Scalability on demand Easy to launch required servers & shut them down when traffic falls EC2 Joyent Rackspace

27. Questions? Thank you for listening!