How element-hq/synapse works
Synapse is a Matrix homeserver: it serves client and administrative APIs, manages room events and user activity, federates with other homeservers, and persists server state. The tree shows distinct API, event/handler, federation, media, push, and storage subsystems, with worker processes supporting deployment across instances. The excerpts confirm homeserver setup and typing-state behavior; the source index provides additional import evidence. Many runtime connections are not shown, so the graph omits uncertain links rather than inferring a complete request pipeline.
Main entry points: server.py Homeserver · federation_client.py Federation client · client Client API · typing.py Typing state
Components 22
HTTP APIs
- Client API
synapse/rest/client - Admin API
synapse/rest/admin - HTTP server
synapse/http/server.py
Rooms and Users
- Event builder
synapse/events/builder.py - Room versions
synapse/api/room_versions.py - Typing state
synapse/handlers/typing.py - Sync handlers
synapse/handlers/sync.py
Federation
- Federation client
synapse/federation/federation_client.py - Federation transport
synapse/federation/transport/client.py - Outbound transactions
synapse/federation/sender/transaction_manager.py
Persistence and Runtime
- Homeserver
synapse/server.py - Configuration
synapse/config/homeserver.py - Event storage
synapse/storage/databases/main/events_worker.py - Database layer
synapse/storage/database.py - Worker replication
synapse/replication/tcp/handler.py - Logging context
synapse/logging/context.py - Tracing
synapse/logging/opentracing.py - Metrics
synapse/metrics/__init__.py
Media and Notifications
- Media API
synapse/rest/media - Media storage
synapse/media/media_storage.py - Push notifications
synapse/push
Other components
- Matrix clients
Connections 13
- Matrix clients → Client API: sends requests
- Client API → HTTP server: uses HTTP
- Homeserver → Configuration: uses config
synapse/server.py - Homeserver → Database layer: sets up stores
synapse/server.py - Event storage → Database layer: uses database
synapse/storage/database.py - Federation client → Federation transport: uses transport
synapse/federation/federation_client.py - Outbound transactions → Federation client: uses client
synapse/federation/sender/transaction_manager.py - Media storage → Media API: supports media
synapse/rest/media/v1/media_storage.py - Homeserver → Event builder: provides builder
synapse/server.py - Federation client → Event builder: uses builder
synapse/federation/federation_client.py - Homeserver → Typing state: provides services
synapse/handlers/typing.py - Typing state → Event storage: reads state
synapse/storage/databases/main/events_worker.py - Homeserver → Metrics: sets up metrics