Valora esta página
AINIA · Original logoAINIA
Success story · R&D and laboratories
AINIA · Portavo
Software architecture · Service continuity

A failure we could not prevent. Monitoring that could keep running.

For AINIA, a technology centre specialising in research and development, we addressed a critical continuity issue: failures when connecting to sensors could close the application and interrupt the monitoring of ongoing laboratory analyses.

AINIA / Portavo · Project screenshot
Original screenshot of the AINIA Portavo projectOriginal project screenshotImage hosted by MyTaskPanel
Laboratory monitoringFailure recoveryIsolated components

Original case-study image · Click to enlarge

Technologies listed in the original case study
C#IISREST API
01 / The challenge

A memory error could interrupt a laboratory analysis in progress.

The laboratory application had to monitor several sensors to collect metrics from analyses in progress. Under certain conditions, connecting to these sensors caused a catastrophic error that closed the program and stopped monitoring.

The issue could not be resolved from within the main application: the failure corrupted memory pointers, making conventional in-process recovery impossible.

We could not ensure the underlying failure would never occur. We could ensure it would not bring down the entire system.

What needed protecting

01

Continuous monitoring

Prevent a component failure from interrupting the monitoring of samples.

02

Failure isolation

Protect the main application from errors in the sensor connection.

03

Automatic recovery

Detect an incident and restore the auxiliary service.

02 / Our contribution

Three separate applications to contain failures and restore service.

We assessed the complexity of the problem and designed an architecture in which sensor communication was isolated from the main application, with a third application responsible for monitoring.

How the solution is structuredCONCEPT DIAGRAM
01

Main application

Keeps laboratory operations running independently of the failing process.

02

Sensor application

Handles sensor connections and can fail without closing the main application.

03

Monitoring application

Detects an auxiliary service failure and restores it.

↗ The failure remains contained; the main application is not interrupted.
Conceptual representation based on the project description; not a product screenshot.
01 · Diagnosis

Understand the failure

We analysed system behaviour and the limits of recovery after memory errors.

02 · Architecture

Separate responsibilities

We isolated the main application from the process responsible for communicating with sensors.

03 · Monitoring

Recover without stopping

We created a third process to detect failures and restart the secondary component.

Outcome: service restored within seconds during testing.The main application continued running without being affected by the auxiliary component failure.
AINIA · Portavo · MyTaskPanel Consulting success storyExplore more success stories ↗