Scaling to $1 Billion: Eventbrite's CTO Shares Lessons Learned

Scaling to $1 Billion

Renaud Visage / co-founder & cto / www.eventbrite.com / twitter @renaudvisage

me
Civil engineer by training
Fell in love with the web in 1998
Self-taught
Developer for photo-sharing pioneer Zing
Co-founded Eventbrite in 2006


why eventbrite?


we built the largest social event
ticketing and discovery platform


$1B in cumulated ticket sales


$600M in ticket sales
in 2012 alone


Series E
May 2011
$50M

Series D
Oct 2010
$20M
Series C
Series B Nov 2009
Series A $6.5M
Nov 2006 Jun 2008
$250k $1.3M


here is how we did it and
what we learned


2006
one engineer
custom python framework
mysql database
apache
all on 1 server!


wearing many hats...


Designer
Graphist
Architect
Manager Sys Admin
Front-End
Spam Expert
IT Guy SEO Expert
Coder
Back-End
Project Manager
DBA


it's all on you to make it
happen


have expert friends you can
call


the importance of making a
good first impression


monitor everything and
anticipate scaling bottlenecks


constantly upgrade and
separate the pieces
before they break
(if possible)


split the database and
web server


don't forget to
back the hell up!


build redundancy


scale prudently as your
traffic grows


make sure you DB has room to
grow and enough memory

2GB RAM 64GB RAM


missing DB indexes will kill
you...


be prepared for anything...


...obama might take you down


...your hosting provider
might take you down


constantly watch technology
evolve and adapt


some landmark moments and
why it's never too late to do
the right thing


2008

build an API
expose your data


2008

offload email sending


2009

start caching data
MySql says


2009

master-slave replication


2009

move to EC2
painful but so worth it


2010

start using load-balanced
slave pool for reads


2010

start writing
unit and automation tests
(yes way late but again better
than never)


2010

switch to git for source control


2010

give Django some love


2010

introduce feature flags


2010
automate server
deployment, server
configuration and release
process in 2010


2010

replace apache with
haproxy+nginx for load
balancing and nginx+uwsgi for
web servers


2010

define coding standards, and
enforce formal code review
process


2010

develop on virtual machines


2011

use queueing system for
async processes


2011

build ticket queue service for
fast-selling events


2011
big push for big data
for reporting, fraud, spam,
event recommendations


2012

front-end automation tests


2012

build specialized and
independant services


2012
180 servers in production today
 big data (30%)
 web servers (25%)
 databases (10%)
l oad balancers (10%)
 queue servers (10%)
 apps, ops, email, etc (15%)


2012
Big data processed per day
2 GB of transactional data
 11 M log lines
 15 GB of log data
 3.5 TB of social data analyzed
 1.2 trillion edges
 30-machine hadoop cluster with 2TB of RAM


lessons learned along the way


expect the unexpected


welcome the challenges that
success brings


stay lean...


...but recognize when you
need help


hire smarter than you


hire generalists to start up and
specialists to scale to the
next level


instrument and monitor
everything


add process as you
scale the team


iterate to improve on
what you have


and don't forget to...


...have fun!


Scaling to $1 Billion: Eventbrite's CTO Shares Lessons Learned

Empfohlen

Empfohlen

Weitere ähnliche Inhalte

Andere mochten auch

Andere mochten auch (15)

Ähnlich wie Scaling to $1 Billion: Eventbrite's CTO Shares Lessons Learned

Ähnlich wie Scaling to $1 Billion: Eventbrite's CTO Shares Lessons Learned (20)

Kürzlich hochgeladen

Kürzlich hochgeladen (20)

Scaling to $1 Billion: Eventbrite's CTO Shares Lessons Learned