T3CONNA 2013

1. Web Applications
High Performance
…in the cloud
T3CON NA- San Francisco - May 30, 2013

2. Fabrizio
BrancaLead System Developer at

3. San Francisco, CA
Janine
Fiona
that’s me
It’s a boy!

4. E-Commerce:
Magento
CMS:
TYPO3
Portals:
ZF, FLOW,…
Mobile Searchperience:
SOLR
120 people
in 7 offices
world-wide
High
Performance
/Scale
Global
Enterprise
Projects

6. PC games (download)
Plush toys, shirts, ...

7. > 24.000.000 likes > 500.000 followers
Social Media
Impact

8. Magento TYPO3
both run on a
“LAMP” stack

9. your application
one process of…
execution time
memory

11. that’s your server
…running your
application

12. 𝑡𝑜𝑡𝑎𝑙 𝑚𝑒𝑚𝑜𝑟𝑦 = 𝑐𝑜𝑛𝑐𝑢𝑟𝑟𝑒𝑛𝑡 𝑢𝑠𝑒𝑟𝑠 ∗ 𝑚𝑒𝑚𝑜𝑟𝑦/𝑝𝑟𝑜𝑐𝑒𝑠𝑠
256 MB
/process
100 users
25 GB RAM
1000 users250 GB RAM

13. Option 1
Make your app “smaller”
make it
faster!make it
consume less
memory!

14. Option 2
Make your box “bigger”
a.k.a.
“vertical scaling”

15. Option 3
Add more boxes
a.k.a.
“horizontal scaling”

16. Vertical
Scaling
Optimization
Horizontal
Scaling
bigger
box
more
boxes
smaller “app”
Scaling

17. Single Server
Multi-Server
vs.
Single server
vs. Multi server
What’s the big deal?

18. Shared nothing?
Session
Storage
Cache
Code
JS/CSS
bundles
DatabaseAssets

19. Multi Server
Deployment

20. “Hello World!
Free Shipping
for everyone!”
“Check out
our new
product!”
“Holiday
Season!”

22. Slow response
times, server
crashes,…

23. Waste of
money

24. Waste of
money
Slow response
times, server
crashes,…

25. Auto Scaling!
Pay per hour

26. Actually, it
looks more
like this

27. Cloud
(in case you haven’t
noticed…:)

29. Amazon EC2 Amazon S3 Amazon RDS
CloudFront
Route 53ElastiCache Elastic Load
Balancing
Cloud Services
AWS Management
ConsoleRightScale Amazon SWFOpsWorks
AWS
CloudFormation

30. EC2 instance

31. EC2 instance
Server Array
(or “auto-scaling group”)
Based on
various metrics

32. Server Array
(or “auto-scaling group”)
EC2 instance

33. Server Array
(or “auto-scaling group”)
EC2 instance

34. Elastic
Architecture
Booting new
instances
fully automatic
Auto-healing
Infrastructure
as Code

35. Loose
Coupling
No hardcoding!
“RightScale API, give
me all frontend
servers”
“ELB, here I am”

36. S3
Deployment X
Backend
Array
Frontend
Array
Worker
Array
Varnish
Array
S3 RDSElastiCache
CloudFront CloudFrontRoute 53
shop.angrybirds.com
Braintree
MailDRM
Giftcards
ELB

37. ELB
Backend
Array
Frontend
Array
Worker
Array
Varnish
Array
Deployment X
Route 53

38. Deployment X+1
Worker
Array
nt X
Route 53
ELB
Backend
Array
Frontend
Array
W
Varnish
Array

39. Worker
Array
nt X
Route 53
Backend
Array
Frontend
Array
W
Varnish
Array
Deployment X+1
ELB

40. Route 53
Backend
Array
Deployment X+1
Frontend
Array
Worker
Array
Varnish
Array
Deployment X
ELB ELB

41. Downtime
Number of
lost carts
Number of
lost sessions
and logins

42. 1.000.000unique visitors. per day.

43. concurrent users.

44. Orders.
10
5 6
7
8
9
per second.
Yes, per second!

45. AppVarnish
Reverse Proxy
Protecting
the application
Only a few
requests hit your app!

46. 90%
Varnish
Tweaking
Cache Hitrate

47. 80%
Varnish
Tweaking
Cache Hitrate

48. 98.6%
Varnish
Tweaking
Cache Hitrate

49. Reduce
Number of Requests
… hitting your application

50. Use a
CDN

51. Offload
dynamic
parts
Do
Ajax

54. Request a page (HTTP Request)
deliver static page
Request
Delivering static content
Placeholders for dynamic parts.
Cache-Control headers
Ajax call request dynamic parts
and transfers the id of the currently visited product
JSON response with dynamic content
Replace placeholder
Write session id to cookie
Render the page
Browser Varnish Application

55. use cookies or
localStorage
Don’t
Ajax

56. Request a page (HTTP Request)
deliver static page
Request
Delivering static content
Placeholders for dynamic parts.
Cache-Control headers
Ajax call request dynamic parts
and transfers the id of the currently visited product
JSON response with dynamic content
Replace placeholder
Write session id to cookie
Render the page
Browser Varnish Application

57. 3xx
4xx
5xx
Redirects
Client errors
Cache other
status codes
Server errors

58. http://example.com/
?utm_source=T3CON
&utm_medium=slides
…and many more.
Normalize
URLs
Filter these!

59. Reduce
Number of Requests
… hitting your application
Don’t AjaxDo Ajax
3xx
4xx
5xx
Cache other
status codes
http://example.com/
?utm_source=T3CON
&utm_medium=slides
Normalize URLsUse a CDN

60. Bottleneck
Candidates
Dynamic requests
are still too slow?

61. RAM
& CPU
That’s easy…

62. DatabaseThat’s not so easy…
offload the
database
less queries
(caching!)
more efficient
queries
(indexes,…)
scaling
sharding
master/slave
Percona Toolkit
(slow) query log

63. Growing
Data
Trimming
the fat!
Orders
Promotions
cms / banners

64. File I/O
especially on
virtual machines!

65. External
Components Frontend?
Cache
Backend?
Web Services?
Webserver?

66. Bottleneck
Candidates
Memory CPU File I/ODatabase
External
Components

67. Launch!
Deployment
Space game
launch!
USA wakes up

68. Thank you!
Any questions?
http://www.aoemedia.com
http://www.fabrizio-branca.de
@fbrnc
Follow me on twitter!
My blog