At the microXchg conference, held in Berlin, Adrian Cockcroft presented “Analyzing Response Time Distributions for Microservices”. Cockcroft demonstrated how the combination of his Spigo microservice architecture simulation tool and the online Guesstimate Monte Carlo method tool can be used to visualise and experimentally simulate request response times within a complicated microservice system.
Amazon recently announced changes to the way customers can monitor their AWS resources. The service, known as CloudWatch Events, allows customers to consume a near real-time stream of events as changes to their AWS environment take place. These event changes can subsequently trigger notifications, or other actions, through the use of rules.
For a long time now developers have been asking why Visual Studio hasn’t made to switch to 64-bit. Rather than effort or opportunity cost, the primary reason is performance. Rico Mariani of Microsoft explains.
Klaus Leopold gave a talk at the GOTO Berlin 2015 conference in which he elaborated why focusing on team-level performance often leads to local suboptimalization and doesn't increase agility across the team. InfoQ interviewed him about why installing agile frameworks does not help to increase agility, how kanban can be used to increase collaboration, and benefits that teams can get from kanban.
Kevin Goldsmith talked about how Spotify uses microservices to break down architectures and be innovative at the GOTO Berlin 2015 conference. He argues that Microservices are easier to test, deploy and monitor than monolithic applications. Spotify also aims to have as few as possible dependencies in their product, and microservices are very helpful for that.
People can tell stories and express themselves when trying to solve complex problems using Lego. Jens Hoffmann facilitated the session "Prototyping an Agile Culture with LEGO® SERIOUS PLAY®" at the GOTO Berlin 2015 conference.
At DockerCon EU 2015 Brian Christner presented an overview of ‘Docker Monitoring’ and shared best practices, a guide to the Docker stats API, and a comparison between three popular monitoring options: cAdvisor, ‘cAdvisor + InfluxDB + Grafana’, and Prometheus.
James Lyndsay did a workshop titled "a nest of tests" at the Agile Testing Days 2015. In this workshop he explored how you can design large collections of tiny tests and visualize their output to test systems, and showed how tools can help you to do it. InfoQ interviewed him about this testing approach.
Plumbr has launched a new Application Performance Management product in their performance monitoring toolkit, that automatically reports on which technical errors are the root cause for performance incidents that impact the end user, linking those to source code.
Runscope, an API monitoring and testing vendor, announced the general availability of Live Traffic Alerts, a real time API performance monitoring solution for live production traffic for key API transactions. InfoQ used this opportunity to speak to Runscope about their vision and the value their platform brings to its consumers.
Obeya is a management approach that uses war rooms and visualization for managing projects. InfoQ did an interview with Malika Mir about why she decided to implement Obeya, how they are using Obeya to manage project portfolios, their experiences with Obeya and the benefits that they have got from it.
Vishal Sikka, CEO of Infosys announced that Infosys has stopped using the bell curve phenomenon which is used to evaluate its 176,000 employees' performance.
In theory the operations team determines what the thresholds for warnings and alerts should be. But in practice, the operations team often have no idea what these values should be. Using machine learning techniques such as adaptive thresholds, Splunk ITSI solves this problem.
Optimizing queries in Splunk’s Search Processing Language is similar to optimizing queries in SQL. The two core tenants are the same: Change the physics and reduce the amount of work done. Added to that are two precepts that apply to any distributed query.
When working with Hadoop, with or without Hunk, there are a number of ways you can accidentally kill performance. While some of the fixes require more hardware, sometimes the problems can be solved simply by changing the way you name your files.