pinboard August 29, 2014

• The Things They Googled | Re/code
• Amazing photo of the Milky Way arching over Yellowstone National Park (Image: Dave Lane) apod.nasa.gov/apod/ap140827.… pic.twitter.com/gvFJblqCbH
• People dying of Sepsis because Antibiotics ‘not working’ bbc.in/1tpHEFI
• Put On Your Streaming Shoes | Shine Technologies
• Storm (event processor) – Wikipedia, the free encyclopedia
  Storm is a distributed computation framework written predominantly in the Clojure programming language. Originally created by Nathan Marz[1] and team at BackType,[2] the project was open sourced after being acquired by Twitter.[3] It uses custom created "spouts" and "bolts" to define information sources and manipulations to allow batch, distributed processing of streaming data. The initial release was on September 17, 2011.[4]

  A Storm application is designed as a topology of interfaces which create a "stream" of transformations. It provides similar functionality as a MapReduce job with the exception that the topology will theoretically run indefinitely until it is manually terminated.[5]

  In 2013 the Apache Software Foundation has accepted Storm into its incubator program.[6][7]

• Apache Storm
  Apache™ Storm is a distributed real-time computation system for processing fast, large streams of data. Storm adds reliable real-time data processing capabilities to Apache Hadoop® 2.x. Storm in Hadoop helps capture new business opportunities with low-latency dashboards, security alerts, and operational enhancements integrated with other applications running in their Hadoop cluster.
• Announcing Apache Kafka Technical Preview in HDP 2.1
  Apache Kafka is a fast, scalable, durable, and fault-tolerant publish-subscribe messaging system. Kafka is often used in place of traditional message brokers like JMS and AMQP because of its higher throughput, replication, and fault tolerance.
• Google unveils secret drone project – San Jose Mercury News
• Introducing Rudder: An etcd backed overlay network for containers
  As we have previously blogged, Kubernetes, the container cluster manager, works great with CoreOS to distribute a workload across your entire cluster. To make it easier to find your services, Kubernetes does away with port-mapping and assigns a unique IP address to each pod. This works well on Google Compute where each host is assigned a /24 for use by individual pods. Things are not as easy on other cloud providers where a host cannot get an entire subnet to itself. Rudder aims to solve this problem by creating an overlay mesh network that provisions a subnet to each server.

  While Rudder was originally designed for Kubernetes, it is a generic overlay network that can be used as a simple alternative to existing software defined networking solutions.

• Gitlab Community Edition on Google Compute Engine – GitLab Community Edition on Google Cloud — Google Developers

Digest powered by RSS Digest