This week, memcached, a piece of software that prevents much of the Internet from melting down, turns 10 years old. Despite its age, memcached is still the go-to solution for many programmers and sysadmins managing heavy workloads. Without memcached, Ars Technica would likely be unable to serve this article to you at all.
Brad Fitzpatrick wrote memcached for LiveJournal way back in 2003 (check out the initial CVS commit here). While waiting for new hardware to help save the site from being overloaded, Fitzpatrick realized that he had plenty of unused RAM spread across LiveJournal's existing servers. He wrote memcached to take advantage of this spare memory and lighten the load on the site.
memcached is a distributed in-memory key-value store that uses a very simple protocol for storing and retrieving arbitrary data from memory instead of from a filesystem. To store a value, a program connects to the memcached server on the default port of 11211 and issues a series of basic commands. (Note: a binary protocol is also supported.)
PALO ALTO, Calif., May 21, 2013 — At a live event today, VMware (NYSE: VMW) CEO Pat Gelsinger unveiled VMware vCloud® Hybrid Service™, an Infrastructure as a Service (IaaS) cloud operated by VMware and built on the trusted foundation of VMware vSphere®, giving customers a common platform to seamlessly extend their data center to the cloud.
“VMware’s mission is to radically simplify IT and help customers transform their IT operations,” said Pat Gelsinger, CEO, VMware. “Today, with the introduction of the VMware vCloud® Hybrid Service™, we take a big step forward by coupling all the value of VMware virtualization and software-defined data center technologies with the speed and simplicity of a public cloud service that our customers desire.”
vCloud Hybrid Service will seamlessly extend VMware software used by hundreds of thousands of customers into the public cloud. This means customers will be able to extend the same skills, tools, networking and security models across both on-premise and off-premise environments.
All of these questions are variations on "Why did Yahoo! spend one-third of their cash on hand to buy a company that by all accounts is about to run out of money?" Read this post, and hopefully these questions will not need to be asked again!
Last Friday Facebook blocked Path’s “Find Friends” feature over brewing spam complaints. Shortly thereafter Dave Morin, Path’s CEO, proudly stated that “Path does not spam users,” but the tactics he is defending today are the very same practices that he himself cracked down on as “spam” when he was running the Facebook Platform. I watched the crack-down from the front-row at iLike, an early Facebook platform partner.
Compare Morin’s description of Path’s “feature” to the Facebook policy that was put in place while Morin was the head of developer relations for Facebook Platform. The official Facebook policy was that apps were forbidden from doing exactly what Morin now calls “not spam”:
Build features fast. Ship them. That's what we try to do at GitHub. Our process is the anti-process: what's the minimum overhead we can put up with to keep our code quality high, all while building features as quickly as possible? It's not just features, either: faster development means happier developers.