Introducing SmartStack: Service Discovery in the Cloud
nerds.airbnb.com
Introducing SmartStack: Service Discovery in the Cloud
1–10 of 39 posts
Re: Introducing SmartStack: Service Discovery in the Cloud
#2[deleted]
Re: Introducing SmartStack: Service Discovery in the Cloud
#3I've been hearing good stuff about this for a while - it's awesome to see it open sourced! Setting up a local haproxy to handle service failover / discovery is a really clever solution, and is an awesome approach to encapsulating a bunch of really messy logic.
Re: Introducing SmartStack: Service Discovery in the Cloud
#4> On AWS, you might be tempted to use ELB, but ELBs are terrible at internal load balancing because they only have public IPs.
Yet another reason to run in a VPC, which includes internal-only ELBs as a very useful feature.
Re: Introducing SmartStack: Service Discovery in the Cloud
#5Can someone explain to me what this really is? I don't follow and yes I read the intro.
Re: Introducing SmartStack: Service Discovery in the Cloud
#6ELB will actually do internal load balancing in a VPC using your own custom security groups. Doesn't help if you're not in a VPC, but nowadays the default is for everything to go in a VPC.
Re: Introducing SmartStack: Service Discovery in the Cloud
#7Can someone explain to me what this really is? I don't follow and yes I read the intro.
With a service-oriented architecture (SOA) you basically break your application into distinct services that run across different machines. But you also need a way to find and connect to those services (service discovery). This provides a way of doing that using ZooKeeper and local HAProxy processes.
Re: Introducing SmartStack: Service Discovery in the Cloud
#8ELB will actually do internal load balancing in a VPC using your own custom security groups. Doesn't help if you're not in a VPC, but nowadays the default is for everything to go in a VPC.
Unfortunately, Airbnb is a pretty legacy AWS client; when we started using it, VPC was a much less prominent feature. Migrating to a VPC is a very non-trivial process, especially if you have RDS instances outside the VPC
Re: Introducing SmartStack: Service Discovery in the Cloud
#9ELB will actually do internal load balancing in a VPC using your own custom security groups. Doesn't help if you're not in a VPC, but nowadays the default is for everything to go in a VPC.
Unfortunately, Airbnb is a pretty legacy AWS client; when we started using it, VPC was a much less prominent feature. Migrating to a VPC is a very non-trivial process, especially if you have RDS instances outside the VPC
I'm in the same boat with most of my AWS workload, was created before IGW was available and keep having the same discussion about migrating :-)
Re: Introducing SmartStack: Service Discovery in the Cloud
#10Can someone explain to me what this really is? I don't follow and yes I read the intro.
With a service-oriented architecture (SOA) you basically break your application into distinct services that run across different machines. But you also need a way to find and connect to those services (service discovery). This provides a way of doing that using ZooKeeper and local HAProxy processes.
So I register a new service (or process) to run on metal using Chef. Then Chef installs the service and updates the nerve config running on that metal device. Nerve then keeps a central Zookeeper updated with the status of its local services? Synapse checks for available services in zookeeper that your app may need to use, and then configures a local load balancer for any requests you make?