SmartStack: Service Discovery in the Cloud – Airbnb Engineering

The properties of an ideal solution: – Backends capable of serving requests for a particular service would automatically receive these requests – Load would be intelligently distributed among backends, so no backend is ever doing more work than the rest and so that requests are automatically routed to the least busy backend – A backend that develops problems would automatically stop receiving traffic – It should be possible to remove load from a backend without affecting anything else in the system, so that debugging is possible – There should be perfect introspection, so that you always know which backends are available, what kind of load they are receiving, and from which consumers – Consumers should be minimally affected by changes in the list of backends; ideally, such changes would be transparent to consumers – There should be no single points of failure – the failure of any machine anywhere in the system should have no impact

(Full Story: http://nerds.airbnb.com/smartstack-service-discovery-cloud/ )

Advertisements

No comments yet... Be the first to leave a reply!

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: