making conferences work
Lanyrd.com
Tuesday, 3 May 2011
Lanyrd.com
Definitive databaseof professional events
and speakers
Tuesday, 3 May 2011
Lanyrd.com
Social event recommendationComprehensive speaker profiles
Archive of slides, notes and video
Definitive databaseof professional events
and speakers
Tuesday, 3 May 2011
Lanyrd.com
Demo
Tuesday, 3 May 2011
Lanyrd.com
Tuesday, 3 May 2011
Lanyrd.com
Tuesday, 3 May 2011
Lanyrd.com
Tuesday, 3 May 2011
Lanyrd.com
Tuesday, 3 May 2011
Lanyrd.com
Why does it work?•The right crowdsourcing incentives
•Wiki-style shared ownership
•The parts support the whole
•Twitter!
Tuesday, 3 May 2011
Lanyrd.com
Why Twitter?•It’s where the event discussion happens
•Speakers promote their Twitter accounts
•Follow beats Friend for recommendations
•Culturally amenable to public profiles
Tuesday, 3 May 2011
Lanyrd.com
Twitter as an Identity Platform
•Make assertions about any Twitter user
•Create profiles to be claimed later
•Instant personalisation
•Naturally viral
Tuesday, 3 May 2011
Lanyrd.com
More demos
Tuesday, 3 May 2011
Lanyrd.com
Tuesday, 3 May 2011
Lanyrd.com
(Inspired by Rapportive)Tuesday, 3 May 2011
Lanyrd.com
Tuesday, 3 May 2011
Lanyrd.com
Tuesday, 3 May 2011
Lanyrd.com
Under the hood
Tuesday, 3 May 2011
Lanyrd.com
Calendar•Pull user’s friends/ids.json
•Cache for ten hours
•Store in Redis
•Solr search: attendees:(34722 OR 1312313 OR...
Tuesday, 3 May 2011
Lanyrd.com
Redis set intersection
Tuesday, 3 May 2011
Lanyrd.com
users/search.json
Tuesday, 3 May 2011
Lanyrd.com
friendships/create
Tuesday, 3 May 2011
Lanyrd.com
Load balancer (nginx)
HTTP cache (varnish)
lanyrd.com badges.lanyrd.net
app server(Django/Apache)
app server(Django/Apache)
app server(Django/Apache)
search server(solr master)
search server(solr slave)
search server(solr slave)
Database(MySQL RDS)
K/V store(redis)
background processing
(celery and cron)
caching(memcache)
Tuesday, 3 May 2011
Lanyrd.com
@lanyrd attending #devnest
Tuesday, 3 May 2011
Lanyrd.com
We’re hiring!(soon)
Tuesday, 3 May 2011
Top Related