QCon 2014 London (Vadim Platanov)

375 views

Published on

Published in: Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
375
On SlideShare
0
From Embeds
0
Number of Embeds
5
Actions
Shares
0
Downloads
3
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

QCon 2014 London (Vadim Platanov)

  1. 1. QCon 2014 London
  2. 2. Conference ● ~1000 attendees
  3. 3. Conference ● ~1000 attendees ● 20 tracks
  4. 4. Conference ● ~1000 attendees ● 20 tracks ● 5 talks per track = 100 talks + keynotes
  5. 5. Conference ● ~1000 attendees ● 20 tracks ● 5 talks per track = 100 talks + keynotes ● 7 tracks in parallel (2 solution tracks)
  6. 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. 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. 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. 9. Big Ideas ● Computer Science matters
  10. 10. Big Ideas ● Computer Science matters ● Psychology matters
  11. 11. Big Ideas ● Computer Science matters ● Psychology matters ● Reliability matters
  12. 12. Big Ideas ● Computer Science matters ● Psychology matters ● Reliability matters ● Modularity matters
  13. 13. Big Ideas ● Computer Science matters ● Psychology matters ● Reliability matters ● Modularity matters ● Terabytes of data matter
  14. 14. Big Ideas ● Computer Science matters ● Psychology matters ● Reliability matters ● Modularity matters ● Terabytes of data matter ● Callbacks don’t matter
  15. 15. Bloomin’ marvelous ● Probabilistic data structures ● Trade accuracy for space ● Bloom filter, Count-Min, HyperLogLog
  16. 16. Fault tolerance made easy ● Timeout
  17. 17. Fault tolerance made easy ● Timeout ● Circuit Breaker
  18. 18. Fault tolerance made easy ● Timeout ● Circuit Breaker ● Fail fast
  19. 19. Fault tolerance made easy ● Timeout ● Circuit Breaker ● Fail fast ● Shed load
  20. 20. Fault tolerance made easy ● Timeout ● Circuit Breaker ● Fail fast ● Shed load ● Deferred work
  21. 21. Fault tolerance made easy ● Timeout ● Circuit Breaker ● Fail fast ● Shed load ● Deferred work ● Limited retries
  22. 22. Microservices at Netflix ● Deliver stuff faster
  23. 23. Microservices at Netflix ● Deliver stuff faster ● Encapsulate patterns in libraries
  24. 24. Microservices at Netflix ● Deliver stuff faster ● Encapsulate patterns in libraries ● Autonomous teams
  25. 25. Microservices at Netflix ● Deliver stuff faster ● Encapsulate patterns in libraries ● Autonomous teams ● Multiple service versions at the same time
  26. 26. Microservices at Netflix ● Deliver stuff faster ● Encapsulate patterns in libraries ● Autonomous teams ● Multiple service versions at the same time ● Dynamic endpoint consumption
  27. 27. 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
  28. 28. Offline-first development ● Improve user experience on mobile devices
  29. 29. Offline-first development ● Improve user experience on mobile devices ● Cache resources locally
  30. 30. Offline-first development ● Improve user experience on mobile devices ● Cache resources locally ● Numerous ways to check if browser online
  31. 31. Offline-first development ● Improve user experience on mobile devices ● Cache resources locally ● Numerous ways to check if browser online ● ServiceWorker - intercept requests
  32. 32. 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
  33. 33. Why does general bombard a hill?
  34. 34. Why does general bombard a hill? Because 67% of other successful generals bombard hills!
  35. 35. http://blog.gardeviance.org/

×