Incident management · 2024 – present

Intervento

An incident management platform that connects its web UI and offline app on one shared domain.

Back to all projects
Role
Architecture, technology selection, core development
Timeframe
2024 – present
Context
Primary owner of architecture and core development in the product team
Technologies
Vue 3VuexApollo GraphQLNode.jsExpressSequelizePostgreSQLSocket.IOS3 / MinIOWhisperDockerBitbucket Pipelines

Intervento guides response teams through the entire process: from the initial call through resources and status to documentation. I reworked the architecture, selected the technologies and implemented a large part of the platform.

01

Context

Intervento is the incident management platform for fire services: capturing incidents, assigning people and resources, tracking status, working through checklists and documenting the course of an operation.

Requirements for incident command, offline operation and integrations grew. Rather than adding more features to the existing foundation, the architecture was reassessed and reworked.

02

My contribution

  • Scaffolded the server and client and made the core technology decisions: Vue 3, Apollo GraphQL, Node.js, Express, Sequelize and PostgreSQL.
  • A feature-oriented modular monolith so that the web app and the mobile app share the same domain.
  • Built the GraphQL schema, data model, migrations and permission logic.
  • Designed and implemented the server-side sync journal for the offline app.
  • Integrated Whisper speech recognition, PDF incident reports and the AlarmHub and FloriPlan interfaces.
  • Added webhooks and “Actions” as an integration point and merged them into the integration branch: outbound events with URL masking and traceable execution logs.
  • Conducted code reviews and co-owned the technical direction.
03

Architecture & delivery

  • Client: Vue 3 with Vuex and Apollo Client on a PrimeVue foundation, 64 web routes; maps with OpenLayers.
  • Server: Node.js, Express, Apollo Server and Sequelize ORM on PostgreSQL; around 197 server routes, 190 GraphQL definitions and 252 migrations (master: 238).
  • Files and media through S3-compatible storage (MinIO); real-time via Socket.IO with a cluster adapter and sticky sessions.
  • Server-side sync journal with field-level diffs, idempotent processing and fan-out to other devices and collaborating organisations.
  • Docker for local development plus test and production environments, Bitbucket Pipelines for CI.
System design One domain, two interfaces
Web & mobile
Shared domain
Data layer
Integration
Vue 3 Web JavaScript · PrimeVue
Flutter App Bloc · sqflite
GraphQL API Apollo · schema
REST API mobile · delta sync
Feature modules incidents · resources
Sync journal field-level outbox
Integrations AlarmHub · FloriPlan
PostgreSQL Sequelize
MinIO / S3 documents · reports
AlarmHub · FloriPlan webhook · plan sync
GraphQL REST Sync Sequelize Files Webhook / sync

Web and mobile share the data model and API layer: GraphQL for the web, a dedicated REST API for delta sync and offline writes. The sync journal records what was applied from which device.

Design decisions
  • GraphQL for the web app, REST for the mobile sync path.
  • Feature-oriented modular monolith: one domain, separate interfaces.
  • The sync journal makes offline writes idempotent and traceable per device.

Scroll horizontally to see the full design.

04

The hard parts

01

Changing the architecture without stopping the product

The platform had to keep running while its foundation was rebuilt. Feature boundaries and clear API contracts helped keep the change in deliverable steps instead of risking everything at once.

02

Domain logic instead of CRUD

Incident management is a stateful process with roles, resources, checklists and time. The data model had to represent those states — not just forms that happen to share the same fields.

03

Permissions inside the GraphQL schema

Visibility and actions had to be enforced consistently across schema, resolvers and UI. A permission check in the frontend alone is not a check.

05

Outcome

  • A platform where the web UI and the offline app build on the same domain.
  • An architecture that can absorb new modules and mobile requirements.
  • The technical foundation for Intervento App's offline synchronisation.

Contact

Let's talk about the next role.

I am looking for a position where I can take responsibility for systems and teams as a lead engineer or software architect. Ideally where reliability, data and real-world workflows meet.

Send an email [email protected]

Availability

Region
Thun/Bern
Workload
80%
Work location
On-site, hybrid or remote by arrangement
Travel
Generally yes, scope depending on the role and responsibilities
Start
by agreement