From a Monolithic to a Distributed API Architecture
 at Eventbrite - Presented at APIDays 2013

3,766 views

Published on

Learn how the Eventbrite API evolved from a monolithic architecture to distributed services and what we're going to build next.

Published in: Technology, Business

From a Monolithic to a Distributed API Architecture
 at Eventbrite - Presented at APIDays 2013

  1. 1. ! 
 From a Monolithic to a Distributed API Architecture
 Renaud Visage, Co-Founder and CTO @renaudvisage
  2. 2. 2 million events 150 million tickets sold $1 billion in gross ticket sales in 2013 Events in 179 countries ! 100+ employees in Product + Engineering
  3. 3. api launch = 2008
  4. 4. monolithic
  5. 5. exponential growth 10,000+ applications have been developed using our API ! 15% of Gross Ticket Sales come from events created via the API ! That’s $150 million for this year alone!
  6. 6. eat your own dog food!
  7. 7. application api
  8. 8. Move to SOA
  9. 9. “Discrete and separate units that each concern themselves with the concepts, data and actions of a specific and narrowly defined area.”
  10. 10. benefits Reusability at the macro level ✴ Fast composability ✴ Autonomy and Deep Focus ✴ Stateful only as needed ✴ Common interconnect methodology ✴ Cross platform and third party integration ✴ Operational Scale ✴ Easier Testing ✴
  11. 11. common service layer Synchrony and Response Delivery Methods ✴ Communications Abstraction ✴ Intelligent Routing ✴ Compound Action Structure ✴ Versioning ✴ Traceability and debugging ✴ Error Handling ✴ Governance ✴ Security ✴
  12. 12. modernize our api New code base using Django REST Framework ✴ Backwards-compatible with v1 ✴ Using SOA design principles ✴ Reach feature parity with web platform ✴ Add support for webhooks ✴ Add support for IFTTT ✴
  13. 13. thank you! @renaudvisage

×