InfoQ Homepage application performance management Content on InfoQ
-
Moldable Development: Guiding Technical Decisions without Reading Code
Developers spend most of their time reading code. Moldable Development challenges reading as a means to gather information from the system, by creating custom tools that show the problem in a way that makes it comfortable to understand. The solution typically follows quickly afterward. Glamorous Toolkit is a moldable development environment designed to decrease the cost of custom tools.
-
The Compounding (Business) Value of Composable Ecosystems
Being “free” and open source doesn’t hinder the value of these projects to businesses and end users; rather it unlocks it. The composability of open source ecosystems allows the innovation and value of the whole ecosystem to compound on itself.
-
Analyzing Incident Data across Organizations: Courtney Nash on the VOID
The Verica Open Incident Database (VOID) is assembling publically available software-related incident reports. InfoQ talks with Courtney Nash on their recent findings including how MTT* metrics may not be beneficial, the average time to incident resolution, and the importance of studying near-miss reports.
-
Establishing a Scalable SRE Infrastructure Using Standardization and Short Feedback Loops
This article explores an SRE implementation where the operations team builds and runs the SRE infrastructure and the development teams build and run the services leveraging the SRE infrastructure. This SRE solution enables the software delivery organization to scale the number of services in operation without linearly scaling the number of people required to operate the services.
-
Embracing Cloud-Native for Apache DolphinScheduler with Kubernetes: a Case Study
This article shares how Apache DolphinScheduler was updated to use a more modern, cloud-native architecture. This includes moving to Kubernetes and integrating with Argo CD and Prometheus. This improves substantially the user experience of deploying, operating, and monitoring DolphinScheduler.
-
DevOps and Cloud InfoQ Trends Report – June 2022
This article summarizes how we see the "cloud computing and DevOps" space in 2022, which focuses on fundamental infrastructure and operational patterns, the realization of patterns in technology frameworks, and the design processes and skills that a software architect or engineer must cultivate.
-
How to Fight Climate Change as a Software Engineer
We need to reduce and eliminate greenhouse gas emissions to stop climate change. But what role does software play, and what can software engineers do? Let’s take a look under the hood to uncover the relationship between greenhouse gas emissions and software, learn about the impact that we can have, and identify concrete ways to reduce emissions when creating and running software.
-
Chaos Engineering and Observability with Visual Metaphors
This article introduces a new actor for visualising chaos engineering and observability: metaphors. It provides the conceptual foundations of chaos engineering and observability, presents a state of art of visualisation techniques available in the market and shows how treemaps, gauge charts, geocentric and city metaphors can enrich the spectrum of the visual strategies to observe the chaos.
-
How to Best Use MTT* Metrics to Optimize Your Incident Response
Selecting the correct MTT* metric to improve your incident response is important. If the wrong metric is chosen, the improvements may get lost in the noise of a multivariable equation. This article reviews the various MTT* metrics available and discusses the best scenarios for selecting each one.
-
Why Change Intelligence is Necessary to Effectively Troubleshoot Modern Applications
Change Intelligence is often a missing component in incident management. Successfully correlating monitoring and observability data to arrive allows engineers to arrive at the root cause more rapidly. Telemetry provides the building blocks that enable change intelligence to identify and map the root cause, based on changes in the system and their broader impact.
-
Why the Future of Monitoring Is Agentless
Traditionally, monitoring software has relied heavily on agent-based approaches for extracting telemetry data from systems. Observability requires better telemetry than agents currently provide. OpenTelemetry is driving advances in this area by creating a standard format and APIs to create, transmit, and store telemetry data. This unlocks new opportunities in observability.
-
How Unnecessary Complexity Gave the Service Mesh a Bad Name
There is immense value in adopting a service mesh, but it must be done in a lightweight manner to avoid unnecessary complexity. Take a pragmatic approach when implementing a service mesh by aligning with the core features of the technology, such as standardized monitoring and smart routing, and watching out for distractions.