Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Building High Scale Systems Using Serverless Architecture for a Burning Man Event - Jonathan Zenou - DevOpsDays Tel Aviv 2017

136 views

Published on

DevOpsDays Tel Aviv 2017

Published in: Technology
  • Be the first to comment

  • Be the first to like this

Building High Scale Systems Using Serverless Architecture for a Burning Man Event - Jonathan Zenou - DevOpsDays Tel Aviv 2017

  1. 1. BUILDING HIGH SCALE SYSTEM USING SERVERLESS ARCHITECTURE FOR A BURNING MAN EVENT Jonathann Zenou DevOps DaysTel Aviv 2017
  2. 2. DISCLAIMER • This is not a serverless introduction • This is about replacing • This is a not a complicated solution
  3. 3. HELLO WORLD • Jonathann Zenou • Tel Aviv • DevOps Engineer @ Oracle
  4. 4. MIDBURN.ORG
  5. 5. NUMBERS • Since 2014 • 3rd biggest • 11000 participants • 2500 volunteers • 30 departments
  6. 6. MIDBURNTECH • 50 yearly volunteers • Perks of being a Non-Profit organisation • Open source • Crucial
  7. 7. TECHNOLOGY • Production and Rnd in AWS • SCM in Github (Open source !) • Ruby, NodeJS and Java
  8. 8. SYSTEMS • volunteers system • profile system • gate system • … • ticket selling queue system
  9. 9. PROBLEMATIC
  10. 10. TICKETS SELLING SYSTEM • Sold out • Very high demand in very short time • Lottery ? • 2 flash events • FIFS
  11. 11. 1ST ITERATION • 2014 • Drupal + php + MySQL • Management of the whole tickets process from Drupal
  12. 12. BUT
  13. 13. 1 ST OUTAGE • ~5000 concurrent users • ~20 sessions by user
  14. 14. REMODELLING
  15. 15. REMODELLING • One queuing system • One selling system
  16. 16. 2ND ITERATION • 2015 • Backend : Heroku + Reddis + Ruby • Frontend : Javascript + S3
  17. 17. Frontend CSV
  18. 18. 2015
  19. 19. 2016
  20. 20. 2ND OUTAGE
  21. 21. • a lot of users enter the system • Backend is swamped • Users hit “refresh” • Backend is even more swamped
  22. 22. WHAT WE UNDERSTOOD ?
  23. 23. REMODELLING
  24. 24. 3RD ITERATION • 2017 • Frontend : still Javascript + S3 • Backend : …
  25. 25. CREATE AN API GATEWAY API AS AN AMAZON KINESIS PROXY http://docs.aws.amazon.com/apigateway/latest/developerguide/ integrating-api-with-aws-services-kinesis.html
  26. 26. Amazon API Getaway
  27. 27. Amazon Kinesis Firehose
  28. 28. S3 STATIC SITE LOGIC is the opened queue page up 
 ? No wait 5 seconds and retry
  29. 29. TESTING
  30. 30. CROSSING FINGERS 2nd sale of the year
  31. 31. NUMBERS • 15 minutes • 3315 users • 300 lucky users • 4 seconds • 3 000 000 requests • 0 errors
  32. 32. –Itamar Cohen, Midburn's COO The Midburn community is composed of thousands of people.Not everyone can get a ticket and people can get angry and frustrated from it .With this new system we ensure that at least if someone does not get a ticket it’s not because of a technical issue .
  33. 33. TECH@MIDBURN.ORG MIDBURNTECH @ FB
  34. 34. QUESTIONS ?

×