Serf vs SkyDNS: What are the differences?

# Introduction
Key differences between Serf and SkyDNS.

1. **Protocol Support**: Serf uses a custom gossip protocol that is designed for high availability, fault tolerance, and performance, while SkyDNS is based on the DNS protocol, enabling easy integration with existing tools and infrastructure.
2. **Service Discovery**: Serf provides decentralized service discovery by maintaining a list of members in a cluster, allowing efficient communication and coordination, whereas SkyDNS offers centralized service discovery by mapping service names to IP addresses through DNS resolution.
3. **Scalability**: Serf can scale to thousands of nodes in a cluster due to its decentralized architecture, which minimizes the impact of adding new nodes, while SkyDNS may experience performance limitations as the number of services and nodes increases due to its centralized nature.
4. **Dynamic Membership**: Serf supports dynamic membership changes, allowing nodes to join and leave the cluster without disrupting the overall system, whereas SkyDNS requires manual configuration updates to reflect changes in the service infrastructure.
5. **Event Propagation**: Serf enables event propagation across the cluster for triggering actions based on specific events, facilitating automation and orchestration tasks, unlike SkyDNS, which primarily focuses on service discovery and DNS resolution without event handling capabilities.

In Summary, the key differences between Serf and SkyDNS lie in their protocol support, service discovery mechanisms, scalability, dynamic membership management, and event propagation capabilities.