PROJECT 03 / BACKEND / REALTIME SYSTEMS
CrisisLink.
When every connection matters.
A realtime incident response platform connecting events, people, and information. Designed around timely updates and clear access boundaries.
01 / CONTEXT
The problem.
Incident response involves changing information and different responsibilities. A useful platform needs to keep participants informed while controlling who can access and act on that information.
02 / APPROACH
From question to system.
React presents the incident experience, backed by Node.js, Express, and MongoDB. Socket.IO handles realtime communication, JWT and role-based access control establish access boundaries, and Gemini assists with image severity classification.
03 / ARCHITECTURE & WORKFLOW
How the pieces connect.
A conceptual overview of the project’s main components.
- 01Incident report
- 02Authenticated API
- 03Severity assistance
- 04Realtime updates
04 / IMPLEMENTATION
Decisions that matter.
Use realtime communication deliberately
Socket.IO supports updates that need to reach connected participants without relying solely on page refreshes.
Separate identity and permission
JWT authentication establishes identity; role-based access control governs permitted actions.
Frame AI as assistance
Image severity classification is an assisted signal in the incident workflow, not a claim of guaranteed emergency assessment.
05 / OUTCOMES & LEARNINGS
What the work taught me.
The platform combines 10+ REST endpoints with realtime communication and authenticated roles. The work connects event-driven interfaces, access control, and AI assistance within one application.
Built with.
Interface visuals are illustrative, not application screenshots. Explore the repository for source code and the current implementation.
NEXT CONNECTION / 04