On overview of the advantages that brings the new version of the HTTP protocol. In my view, the most important advantage of this new version is the latency an performance improvements, by using things like multiplexing, binary framing and headers compression.
This paper presents the most exhaustive study of syn- chronization to date. We span multiple layers, from hardware cache-coherence protocols up to high-level concurrent software. We do so on different types of architectures, from single-socket – uniform and non- uniform – to multi-socket – directory and broadcast- based – many-cores. We draw a set of observations that, roughly speaking, imply that scalability of synchroniza- tion is mainly a property of the hardware.
Packer is a tool for creating images in several formats (for Amazon’s AMIs, VMware, Virtualbox, etc), provision them (with puppet, shell, etc). And Vagrant is the best tool for running those images in VirtualBox, Amazon, OpenStack or any other “provider”.
I’ve found Packer a very convenient tool for creating images for ALL the providers Vagrang supports (so you can seamlessly switch between local deployments in VirtualBox to production environments like Amazon), but I’m not sure where is the best place for doing the provisioning stuff… should it be done when creating the image? Or maybe when we start running it from Vagrant?
SkyDNS is a DNS server, made in Go, for dynamic discovery of versioned services.
From the blog:
SkyDNS is our attempt to solve the problem of finding the services that are running in a large environment. SkyDNS acts as a DNS service that only returns SRV records. Services announce their availability by sending a POST with a small JSON payload. Each service has a Time to Live that allows SkyDNS to expire records for services that haven’t updated their availability within the TTL window. Services can send a periodic POST to SkyDNS updating their TTL to keep them in the pool.
I don’t think the Time-to-live feature is particularly useful (you could probably find better solutions for HA in your services), but I like other things like the way it integrates with legacy systems as a regular DNS server, the fact services can register with simple REST calls, the builtin HA based on RAFT…