Meeting Portal
- Microservice Architecture
- Access Separation
- Unified User Profile
- Archive Storage
- Notification Service
For VTB REGISTRATOR JSC, we performed a large-scale redesign of the "Meeting Portal" system: decomposed the monolith into a microservice architecture, separated administrative contours, enhanced security, and integrated a unified user profile through Kvorum ID.
The system is currently in beta testing and preparing for launch for a wide range of users. Core functionality has been implemented and accepted.
Meeting Portal — what was done:
Architecture redesign — transitioned from a monolithic system to a modular one where each component operates independently and scales separately
Administrative role separation — configured access separation for different user categories with individual security policies
Administrative contour protection — management interfaces are protected in accordance with the information security requirements of the financial sector
Notification service — developed a separate service for managing participant notifications about events and status changes
Archive events service — created optimized storage for completed events, which unloaded the main system and improved performance
Unified user profile — implemented integration with the client authorization system for using a unified user profile
Implementation Details
The system is designed based on independent components — each is responsible for its own zone and scales separately. This eliminates a single point of failure and allows the system to evolve without stopping working parts.
Different user groups have access separation with individual rights and security policies.
A flexible authorization system has been implemented, taking into account various user categories and their authorities.
Participant notifications and alerts are moved to a separate independent service. This allows flexible management of channels and notification scenarios without affecting the main system logic.
Historical data about 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 authorization — 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 the task to us — we will propose the optimal work model
We always fix
Cost
Deadlines
Scope of Work