• Before and after lot vacancy

  Justin Blinder used New York's city planning dataset and Google Streetview for a before and after view of vacant lots. …

  • 

• SGI Delivers Shared Memory System for Earth Simulator

  SGI announced that the Japan Agency for Marine-Earth Science and Technology (JAMSTEC) has selected a SGI UV 2000 with Intel Xeon processor E5-4600 v2 series for per and post-processing offline grid simulations for its Earth Simulator supercomputer.

• Open Networking Summit: Brocade Adds OpenFlow Support

  At the Open Networking Summit in Santa Clara, California this week Pluribus Networks announced inNetwork Analytics, Procera Networks' NAVL Engine was selected by GFI Software, and Brocade launches support for OpenFlow 1.3 across its IP portfolio of products.

• Zayo Acquires Dallas Provider CoreXchange

  zColo, the colocation division of international bandwidth provider Zayo Group, has acquired CoreXchange, a data center and managed services provider in Dallas, Texas.

• Five Reasons to Consider Hybrid Cloud Computing

  Many still have questions around one of the most popular cloud models – the hybrid cloud environment. Cloud columnist Bill Kleyman looks at five very real use-cases

• Software-Defined Availability: Redefining Uptime for the Cloud

  Where does the concept of software-defined architectures go next? Look to the cloud, writes Dave LeClair of Stratus Technologies.

• New Owners for Philadelphia Carrier Hotel at 401 North Broad

  Amerimar Enterprises and Abrams Capital have acquired 401 North Broad Street, the major data center and carrier hotel in Philadelphia, and will partner with telecom industry veteran Hunter Newby to operate the property.

  • 

• Netronome Network Cards Accelerate SDN and NFV Designs

  Networking solutions provider Netronome has launched a new platform architecture to augment virtual switch implementations with hardware acceleration NICs in standard servers for software defined networks (SDN) and network functions virtualization (NFV) designs.

• Bliki: CircuitBreaker

  It's common for software systems to make remote calls to software running in different processes, probably on different machines across a network. One of the big differences between in-memory calls and remote calls is that remote calls can fail, or hang without a response until some timeout…

  • 
  • 
  •