The document describes a QCon 2014 London conference that had approximately 1000 attendees, 20 tracks with 5 talks each for a total of 100 talks, and was held in front of the Westminster building. It also lists several "Big Ideas" topics discussed, including how computer science, psychology, reliability, modularity, and large data sets are important. Additional sessions covered probabilistic data structures, fault tolerance patterns, Netflix microservices, and offline-first development.

1. QCon 2014 London

2. Conference
● ~1000 attendees

3. Conference
● ~1000 attendees
● 20 tracks

4. Conference
● ~1000 attendees
● 20 tracks
● 5 talks per track = 100 talks + keynotes

5. Conference
● ~1000 attendees
● 20 tracks
● 5 talks per track = 100 talks + keynotes
● 7 tracks in parallel (2 solution tracks)

6. Conference
● ~1000 attendees
● 20 tracks
● 5 talks per track = 100 talks + keynotes
● 7 tracks in parallel (2 solution tracks)
● In front of the Westminster

7. Conference
● ~1000 attendees
● 20 tracks
● 5 talks per track = 100 talks + keynotes
● 7 tracks in parallel (2 solution tracks)
● In front of the Westminster
● Great food

8. Conference
● ~1000 attendees
● 20 tracks
● 5 talks per track = 100 talks + keynotes
● 7 tracks in parallel (2 solution tracks)
● In front of the Westminster
● Great food
● Free stuff

9. Big Ideas
● Computer Science matters

10. Big Ideas
● Computer Science matters
● Psychology matters

11. Big Ideas
● Computer Science matters
● Psychology matters
● Reliability matters

12. Big Ideas
● Computer Science matters
● Psychology matters
● Reliability matters
● Modularity matters

13. Big Ideas
● Computer Science matters
● Psychology matters
● Reliability matters
● Modularity matters
● Terabytes of data matter

14. Big Ideas
● Computer Science matters
● Psychology matters
● Reliability matters
● Modularity matters
● Terabytes of data matter
● Callbacks don’t matter

15. Bloomin’ marvelous
● Probabilistic data structures
● Trade accuracy for space
● Bloom filter, Count-Min, HyperLogLog

17. Fault tolerance made easy
● Timeout

18. Fault tolerance made easy
● Timeout
● Circuit Breaker

19. Fault tolerance made easy
● Timeout
● Circuit Breaker
● Fail fast

20. Fault tolerance made easy
● Timeout
● Circuit Breaker
● Fail fast
● Shed load

21. Fault tolerance made easy
● Timeout
● Circuit Breaker
● Fail fast
● Shed load
● Deferred work

22. Fault tolerance made easy
● Timeout
● Circuit Breaker
● Fail fast
● Shed load
● Deferred work
● Limited retries

23. Microservices at Netflix
● Deliver stuff faster

24. Microservices at Netflix
● Deliver stuff faster
● Encapsulate patterns in libraries

25. Microservices at Netflix
● Deliver stuff faster
● Encapsulate patterns in libraries
● Autonomous teams

26. Microservices at Netflix
● Deliver stuff faster
● Encapsulate patterns in libraries
● Autonomous teams
● Multiple service versions at the same time

27. Microservices at Netflix
● Deliver stuff faster
● Encapsulate patterns in libraries
● Autonomous teams
● Multiple service versions at the same time
● Dynamic endpoint consumption

28. Microservices at Netflix
● Deliver stuff faster
● Encapsulate patterns in libraries
● Autonomous teams
● Multiple service versions at the same time
● Dynamic endpoint consumption
● Automated cleanup and monitoring

29. Offline-first development
● Improve user experience on mobile devices

30. Offline-first development
● Improve user experience on mobile devices
● Cache resources locally

31. Offline-first development
● Improve user experience on mobile devices
● Cache resources locally
● Numerous ways to check if browser online

32. Offline-first development
● Improve user experience on mobile devices
● Cache resources locally
● Numerous ways to check if browser online
● ServiceWorker - intercept requests

33. Offline-first development
● Improve user experience on mobile devices
● Cache resources locally
● Numerous ways to check if browser online
● ServiceWorker - intercept requests
● CouchDB and www.hood.ie promotion

37. Why does general bombard a hill?

38. Why does general bombard a hill?
Because 67% of other successful generals
bombard hills!

43. http://blog.gardeviance.org/