InfoQ Homepage Infrastructure Content on InfoQ
-
Lyft Replaces Puppet with SaltStack
Lyft, a "ridesharing" start-up, replaced Puppet with SaltStack as its infrastructure configuration management tool. Ansible was the other contender as Ryan Lane, a Lyft engineer, explained in his recent article. In the end, SaltStack came on top when Lyft considered each tool's ease of use, maturity, performance and the surrounding community.
-
CoreOS Launches the CoreOS Enterprise Registry
CoreOS has announced the acquisition of Quay.io and the launch of the CoreOS Enterprise Registry, a private, behind-the-firewall Docker registry, based on Quay.io hosted service.
-
Google unveils Mesa - Geo-Replicated Near-Realtime Scalable Data Warehouse
Google has unveiled their new data-warehouse called Mesa. Mesa is a system that scales across multiple data centers and processes petabytes of data, while being able to respond to queries in sub-second time and maintain ACID properties.
-
The End of .NET 4.0 is Near
Microsoft has announced an end-of-life schedule for .NET 4.0 thru 4.5.1. After January 12 of 2016, all technical support, including security and non-security updates, will be discontinued. Developers and users will need to either go back to.NET 3.5 SP 1 or upgrade to 4.5.2.
-
Oracle Announces First Java 9 Features
Oracle has announced the first set of enhancement proposals that will deliver features for Java 9. They include HTTP/2 support, enhanced JSON support and a first step towards modularity.
-
AppDynamics New Release Brings Big Data and Machine Learning to APM
Leading application performance monitoring vendor AppDynamics released version 3.9 of their flagship "Application Intelligence Platform" monitoring tool. Highlights of the release include big data analysis and machine learning to provide intuitive, scalable performance monitoring. InfoQ spoke to Maneesh Joshi, head of product marketing and strategy at AppDynamics
-
Data Encryption in Apache Hadoop with Project Rhino - Q&A with Steven Ross
Cloudera recently released an update over Project Rhino and data at-rest encryption in Apache Hadoop. Project Rhino is an effort of Cloudera, Intel and Hadoop community to bring a comprehensive security framework for data protection. InfoQ recently talked to Steven Ross from Cloudera team to learn more about the project.
-
Comparing Virtual Machines and Linux Containers Performance
IBM Research Division has published a paper comparing the performance of container and virtual machine environments, using Docker and KVM, highlighting the cost of using Docker with NAT or AUFS, and questioning the practice of running containers inside of virtual machines.
-
ClusterHQ Launches Flocker to Facilitate Robust Stateful Docker Containers
Flocker is a volume and container management system for Docker based on ZFS. It allows for stateful containers, such as databases, to be moved between virtual or physical hosts. This provides a capability that is analogous to the live migration features of some virtual machine hypervisors. Version 0.1 has been released by ClusterHQ as an Apache 2.0 open source project.
-
Flickr Chooses Sentinel for Highly Available Redis
Flickr recently announced that they have deployed Sentinel to provide automated Redis failover in their offline task processing subsystem despite worries about its consistency.
-
Red Hat Releases Project Atomic
In April, Red Hat released Project Atomic, a prototype system for running Docker containers. This is Red Hat’s response to the interest in CoreOS a system for hosting Docker containers based on ChromeOS.
-
Try Before You Buy: Heroku Supports Preview of GitHub Applications
Heroku is trying to make it easier to turn source code into a running application. The Heroku Button – a simple bit of HTML or Markdown that triggers a deployment from a public GitHub repository to Heroku’s public cloud – sets up Heroku as an attractive destination for quickly previewing, hosting, and extending open source web applications.
-
Experiences from Failing with Microservices
Different views within the team on the benefits and drawbacks comparing a microservice architecture with a more traditional monolithic architecture was one of the major reasons we failed, Richard Clayton writes sharing his experiences and reasons for failing when implementing and maintaining a microservice architecture.
-
Striking a Balance Between Open API Usage Policies and Innovation
The limits imposed on open API usage policies by API providers has sparked off a debate on the relationship between such restrictions and its effect on innovation. In spite of philosophical differences between the two sides developers continue to circumvent technical blocks to access data. Is there a way to strike a balance or align interests?
-
Microservices and the Big Ball of Mud
Recently several articles have been written which wonder whether microservices offers a better way of architecting systems or represents a potential problem waiting to happen: distributed Big Balls of Mud. Simon Brown and Gene Hughson discuss the possibility that until people can write well architected monolithic systems they're unlikely to benefit from microservices.