Meeting portal
- Microservice Architecture
- Access control
- Single User Profile
- Archive storage
- Mailing service
For JSC VTB Registrar, we carried out a large-scale redesign of the Meeting portal system: decomposed the monolith into a microservice architecture, separated administrative domains, strengthened security, and integrated a unified user profile through Quorum ID.
The system is currently in beta testing and is being prepared for launch to a wide user audience. Core functionality has been implemented and accepted.
Meeting portal — what was done:
Architecture redesign — moved from a monolithic system to a modular one, where each component works independently and scales separately
Administrative role separation — configured access control for different user categories with individual security policies
Administrative domain protection — management interfaces are secured in accordance with financial sector information security requirements
Notification service — developed a separate service for managing participant notifications about events and status changes
Archived events service — created an optimised storage for completed events, which reduced the load on the main system and improved performance
Unified user profile — implemented integration with the client’s authorisation system to enable a single user profile
Implementation details
The system is designed on the principle of independent components — each responsible for its own area and scales separately. This eliminates a single point of failure and allows the system to evolve without stopping working parts.
Access control with individual rights and security policies has been implemented for different user groups.
A flexible authorisation system has been implemented, taking into account different user categories and their permissions.
Notifications and alerts for participants have been moved to a separate independent service. This allows flexible management of channels and mailing scenarios without affecting the core system logic.
Historical data on completed events is stored separately from current data. The main system works only with current data — this directly affects speed and stability under load.
The system supports federated authorisation — the user logs in through an external trusted service, to which the system fully delegates identity verification. This eliminates duplicate credentials and simplifies access management when working with multiple products.
Ready to discuss your project?
Describe your task to us — we'll suggest the best working model
We always fix
Cost
Deadline
Scope of work