“In turns that the secret is knowing how to break the )scheduling) rules”
A lot of my talks like How GitHub Uses GitHub to Build GitHub and posts like How GitHub Works are great, but they represent a snapshot of the company when we were 30-75 employees. We’re 217 today, and things inevitably changed to grow the company to that scale. This talk is retrospective: it takes a closer look at specific things that I’ve said over the last two years, and then details the adjustments that were made as we’ve grown.
(Full Story: https://speakerdeck.com/holman/how-github-no-longer-works )
Puppet , Chef , Ansible , and Salt  were all built with that very goal in mind: to make it much easier to configure and maintain dozens, hundreds, or even thousands of servers. That’s not to say that smaller shops won’t benefit from these tools, as automation and orchestration generally make life easier in an infrastructure of any size. I looked at each of these four tools in depth, explored their design and function, and determined that, while some scored higher than others, there’s a place for each to fit in, depending on the goals of the deployment. Here, I summarize my findings.
(Full Story: http://www.infoworld.com/print/231308 )
But over the past few years, Java has evolved into something very different. It has quietly become the primary foundation for most the net’s largest and most ambitious operations, including Google, LinkedIn, Tumblr, and Square, as well as Twitter. “It’s everywhere,” says Krikorian. In the summer of 2011, Bob Lee — the chief technology officer at Square and a former engineer at Google — announced at a prominent software conference that the web was “on the cusp of a Java renaissance.” Two years later, this renaissance is upon us. Like Twitter, many other companies have realized that Java is particularly well suited to building web services that can stand up to the massive amounts of traffic streaming across the modern internet. “Java is really the only choice when it comes to the requirements for a company like ours — extreme performance requirements and extreme scalability requirements,” Lee says of Square,
Our leak detection solution grew out of a combination of two things: our own daily need and research interest. It lead us to inventing a method to automatically understand how an application should behave by distinguishing anomalies in its memory usage patterns. And we are on the track of revolutionizing the way you think about monitoring tools.
(Full Story: http://plumbr.eu/about-us )