Enhancing Worker Digital Experience: A Hands-on Workshop for Partners
How Lanyrd uses Twitter
1. Lanyrd.com
making conferences work
Tuesday, 3 May 2011
2. Lanyrd.com
Definitive database
of professional events
and speakers
Tuesday, 3 May 2011
3. Lanyrd.com
Definitive database Social event recommendation
of professional events Comprehensive speaker profiles
and speakers Archive of slides, notes and video
Tuesday, 3 May 2011
9. Lanyrd.com
Why does it work?
•The right crowdsourcing incentives
•Wiki-style shared ownership
•The parts support the whole
•Twitter!
Tuesday, 3 May 2011
10. 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
11. 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
18. 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
19. Lanyrd.com
Redis set intersection
Tuesday, 3 May 2011
20. Lanyrd.com
users/search.json
Tuesday, 3 May 2011
21. Lanyrd.com
friendships/create
Tuesday, 3 May 2011
22. Lanyrd.com
lanyrd.com badges.lanyrd.net
Load balancer HTTP cache
(nginx) (varnish)
app server app server app server
(Django/Apache) (Django/Apache) (Django/Apache) background
caching
(memcache) processing
(celery and cron)
search server search server search server
(solr master) (solr slave) (solr slave)
K/V store Database
(redis) (MySQL RDS)
Tuesday, 3 May 2011
23. Lanyrd.com
@lanyrd attending
#devnest
Tuesday, 3 May 2011
24. Lanyrd.com
We’re hiring!
(soon)
Tuesday, 3 May 2011