Diese Präsentation wurde erfolgreich gemeldet.
Wir verwenden Ihre LinkedIn Profilangaben und Informationen zu Ihren Aktivitäten, um Anzeigen zu personalisieren und Ihnen relevantere Inhalte anzuzeigen. Sie können Ihre Anzeigeneinstellungen jederzeit ändern.

AirBnB service auto discovery

Growing from single monolith app to service oriented architecture. The new problems and how AirBnB are doing service auto discovery.

  • Loggen Sie sich ein, um Kommentare anzuzeigen.

AirBnB service auto discovery

  1. 1. AirBnB Service Autodiscovery Stockholm Python Meetup Jun 16, 2016
  2. 2. About me Ilian Iliev Platform Engineer ilian@lifesum.com www.ilian.io
  3. 3. Starting as a monolith ● Easy at the beginning ● Hard to scale later ● Hard to detach apps ● Solution?
  4. 4. Services ● Small(er) ● “Independent” ● Talking to each other ● Easier to deploy and scale ● Is SOA the ultimate solution?
  5. 5. New problems ● Routing traffic to the correct service ● Adding and removing new instances to the pool ● What if an instance dies?
  6. 6. A perfect solution requirements ● Routing ● Load balancing ● Health status ● Debug single node ● Introspection ● Safe to changes in the pool ● No single point of failure
  7. 7. Suboptimal solutions ● DNS ● Central load balancing ● In App registration/discovery
  8. 8. Smart stack ● Nerve - service registration ● Synapse - service discovery
  9. 9. Nerve
  10. 10. Synapse
  11. 11. Benefits ● Immediate discovery ● Problem are detected on small intervals ● Easy to debug ● Introspection ● Distributed infrastructure
  12. 12. The future ● Zookeeper is still critical ● Dynamic Nerve config
  13. 13. Questions?

×