BUILDING FOR MASSIVE TRAFFIC

Kenneth SolbergAlex Norcliffe

• About

• Development

• Handling traffic

The talk

• Wired• Strategy and goals• Why Umbraco?

– Rapid development– Open-source

• No license fees for the product• Share costs – become part of an evolving platform• Avoid buying limited access to a vendor• Leave more budget for creating great sites

– Re-use content across multiple sites and domains– Host many sites on one server set-up– Non-technical user interface– Low cost of support

About

• Dislocated development teams

• Source control and continous integration

• Shared database

• Side-by-side dev and content production

Development

• What’s ”massive”?

– Unpredictable traffic pattern

– Timezone of audience spread across globe

– Large amount of content: cache turnover rate

– High amount of pageviews

• CondeNet UK + Italy combined = >100m PVs per month

Massive Traffic

• Scaling the code

– Code performance before adding caching

• JetBrains dotTrace code profiler

• Even String.Concac rather than String.Format!

– WebCacheManager framework

– Lucene indexing of external data sources

• Comments, Image + Video assets

– OutputCaching ”icing the cake”

Massive Traffic

• Scaling the hardware

– Multiple web servers

– Load balancers

– NAS for common storage

• Umbraco issues and workarounds

Massive Traffic

• Monitoring

– Performance diagnostics

– Self management (open session tmrw)

• App startup/shutdown alerts to dev team

• Error monitoring on steroids

– External ping services (Pingdom, SiteConfidence)

– Don’t let the client be your alerting service

Massive Traffic

Q&A

• Alex Norcliffe, Boxbinary.com

– Email: alex.norcliffe@boxbinary.com

– Twitter: alex_norcliffe

– Blog: Coming soon!

• Kenneth Solberg, Xeed.no

– Email: kenneth@xeed.no

– Twitter: kenneths

– Blog: http://kenny.no/

Thank you!

Support slides

Custom datatypes

DAM

Infrastructure