You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Confero is a real-time communication platform designed for low-latency video and voice interactions.
3
+
Confero is a real-time skill-based video networking platform designed for low-latency video and voice interactions.
4
4
5
-
The project focuses on clean architecture, scalability, and practical real-world implementation of real-time systems using modern web technologies.
5
+
The project focuses on clean architecture, scalability, and practical real-world implementation of real-time systems using modern web technologies. Users create profiles with skill tags, enter a matchmaking queue, and are paired with someone who shares at least one skill — a live WebRTC video call begins automatically.
6
6
7
7
---
8
8
@@ -14,91 +14,183 @@ The codebase follows a **monorepo architecture**, keeping frontend and backend d
14
14
15
15
The goal is to build a system that is predictable under load, easy to reason about, and extensible for future features.
16
16
17
+
<br/>
18
+
19
+
20
+
17
21
---
18
22
19
23
## Key Features
20
24
21
-
- Real-time video and audio communication
22
-
- WebSocket-based signaling layer
23
-
- WebRTC peer-to-peer media streaming
24
-
- Multi-user room support
25
-
- Asynchronous event handling
25
+
- Real-time video and audio communication via WebRTC P2P
26
+
- WebSocket-based signaling layer with Socket.IO
27
+
- Skill-intersection matchmaking backed by Redis queues
28
+
- Two-sided readiness gate — call only starts when both users accept
29
+
- Duplicate tab guard using Redis `SCARD` checks
30
+
- OTP + Google OAuth 2.0 authentication
31
+
- JWT HTTP-only cookies with refresh token rotation
<tdalign="center"><sub>Profile with skill overview</sub></td>
84
+
<tdalign="center"><sub>Live banner update with toast confirmation</sub></td>
85
+
<tdalign="center"><sub>Full profile — personal info & expertise</sub></td>
86
+
</tr>
87
+
</table>
88
+
89
+
---
90
+
91
+
## Admin Panel
92
+
93
+
A full admin console gives platform operators real-time visibility — active socket connections, live call sessions, total video calls, match rate, call time distribution, and a searchable connection log.
├── WebRTC (Media Streams — direct P2P, no server touch)
66
156
│
67
-
└── REST APIs
157
+
├── WebSocket Signaling ──► Live Service ──► Redis (presence, queues, locks)
158
+
│ │
159
+
│ └── RabbitMQ ──► Auth Service (session recording)
68
160
│
69
-
├── Redis (Presence, ephemeral state)
70
-
├── RabbitMQ (Async events)
71
-
└── Core Services
161
+
└── REST APIs ──► API Gateway ──► Auth Service (users, auth, admin)
162
+
(rate limiting,
163
+
reverse proxy)
164
+
```
165
+
166
+
This separation allows real-time media traffic to remain fully isolated from control logic and background processing. A database write failure never interrupts a live call.
167
+
168
+
---
72
169
73
-
This separation allows real-time media traffic to remain isolated from control and background processing logic.
Managed using **pnpm workspaces** for consistent dependency control.
74
179
75
180
---
76
181
77
182
## Design Principles
78
183
79
184
- Explicit over implicit behavior
80
-
- Clear separation of concerns
185
+
- Clear separation of concerns — controllers thin, logic in services, data access in repositories
81
186
- Real-time paths kept minimal and fast
82
187
- Event-driven workflows for non-blocking operations
83
188
- Maintainability prioritized over shortcuts
84
189
85
190
---
86
191
87
-
## Monorepo Structure
88
-
89
-
-`apps/web` – Frontend (Next.js)
90
-
-`apps/server` – Backend services
91
-
-`packages/shared` – Shared types and utilities
92
-
93
-
Managed using **pnpm workspaces** for consistent dependency control.
94
-
95
-
---
96
-
97
192
## Status
98
193
99
-
**Active development**
100
-
101
-
Core real-time communication and signaling infrastructure is in place.
102
-
Additional scalability, observability, and reliability improvements are ongoing.
194
+
**Active development.**
103
195
104
-
---
196
+
Core real-time communication and signaling infrastructure is fully operational and deployed on Azure. Additional scalability, observability, and reliability improvements are ongoing — including moving call state to Redis for horizontal scaling and establishing test coverage starting with the matching engine.
0 commit comments