Consent Preferences

Accelerating System Updates for a Leading Financial Analytics Provider

Separating a financial data interface into its own delivery flow, so new capabilities could be released without waiting for core website updates.

Quick Insights

Independent ownership

by moving team-owned areas into a dedicated microfrontend.

Lower release dependency

by separating domain-specific updates from the core website shell.

Faster feature rollout

for Risk Indicators, alerts, and permission-aware financial data visibility.

Сontrolled access to financial data

through clearer visibility rules for users with full or partial permission

Client

The client is a leading financial analytics provider that gives subscribers access to financial datasets, ratings-related insights, portfolios, saved searches, and analytical tools used for investment research and risk assessment.

Client Need

The client’s core platform was built as a modular web application, where the core site shell and separate functional areas could be owned by different teams. This created a strong foundation for scalability, but financial data features still needed a clearer path for independent development and delivery.

The client needed the financial data area to evolve without depending on every core website release or adding extra complexity for other platform teams. This required a dedicated delivery setup for the financial data interface and related capabilities, including new datasets, alerts, and more precise permission-based data visibility.

Independent Delivery Requirements

The client’s platform already used a microfrontends architecture, but some financial data interface areas were still tied to the main site repository and release flow. Expert Soft had to strengthen independence at the domain level without changing the broader platform architecture. The solution had to meet several ownership and delivery requirements:

  • Fit the existing microfrontends model. The dedicated financial data interface had to integrate smoothly with the core website shell.
  • Separate domain-specific UI ownership. Financial data pages and components had to move into their own microfrontend and delivery flow.
  • Reduce release dependency. Updates to this area had to be built, tested, and released without waiting for every core site release.
  • Avoid extra complexity for other teams. The separation had to give one domain more freedom without disrupting shared platform workflows.
  • Stay aligned with shared platform rules. New features still had to work with existing data access patterns, permissions, and integration points.

With these requirements in place, Expert Soft focused first on separating ownership for the financial data interface and then used this dedicated delivery path to roll out new platform capabilities more efficiently.

Creating Independent UI Ownership

As part of fintech web development, Expert Soft separated the financial data interface from the main application repository and moved it into a dedicated microfrontend. This gave the domain its own codebase and delivery flow while keeping it connected to the existing platform shell.

The new setup allowed the team to build, test, and release financial data interface updates independently, without waiting for unrelated core website changes. It also kept ownership boundaries cleaner: the broader platform could continue evolving on its own, while the financial data area gained more control over its roadmap and release timing.

This independent delivery path then became the foundation for expanding the platform with new financial data capabilities.

Delivering New Data Capabilities

With the financial data interface separated into its own delivery flow, Expert Soft could expand this platform area without increasing dependency on the core website release cycle. The next stage was to deliver domain-specific capabilities that improved how users access, monitor, and interpret financial data.

Risk Indicators Rollout

Risk Indicators were introduced as a new dataset alongside existing financial fields. Each Risk Indicator corresponded to a financial parameter, followed a defined calculation methodology, and had to be available both through API endpoints and the web interface. The rollout had to fit the existing financial data architecture:

Data ingestion remained outside the user-facing layer

Python-based ETL workflows processed Risk Indicators data and persisted the resulting values in MongoDB.

Java services exposed the data for platform use

API services read Risk Indicators from MongoDB and made them available to downstream consumers.

The central data aggregation layer handled access control

Requests were routed by field ownership, permissions were checked based on metadata, and responses could be combined from multiple services when needed.

The new dataset reused the existing field-based model

Risk Indicators were introduced without changing the overall data access pattern, which helped reduce architectural disruption.

On the interface side, Expert Soft built a dedicated Risk Indicators page where users could select entities and fields, work with saved portfolios, view data in the UI, retrieve it via API, and analyze historical values through line or step charts depending on the data type.

The implementation also had to move in parallel with back-end readiness. Front-end work started before the final Risk Indicators services and data were fully available, so standard financial fields were used as placeholders to validate the UI flow. Once the actual data was ready in MongoDB and services were completed, the page was switched to the real Risk Indicators fields and expanded incrementally.

Alerts Extension

The platform already allowed users to receive alerts when selected parameters changed for entities stored in their portfolios or saved searches. Expert Soft extended this mechanism with a new financial data alert, keeping the implementation aligned with the existing notification infrastructure.

The alert flow reused the platform’s event-based model:

  • A Java-based service detected relevant value changes
    When selected financial values changed, the service prepared an event for the alerting flow.
  • Kafka passed the event into the existing notification pipeline
    The message was published to a predefined topic already expected by the platform’s alerts infrastructure.
  • Downstream services handled final delivery preparation
    The event moved through several services before reaching the SendGrid integration layer.
  • SendGrid managed the email layout through templates
    Expert Soft prepared the JSON payload required by the template instead of generating email content directly in code.

The key challenge was making sure the alert worked across the full chain, not only inside one service. To verify delivery, the team traced messages through Kafka and downstream logs, checked the final SendGrid-integrating service, and triggered real data changes in QA to confirm that the alert email was delivered.

Permission-Aware Financial Data Visibility

The financial data interface needed more precise access behavior for entities that contained different types of financial datasets. For example, one entity could include both banking and non-banking financial data, while a user might have permission to view only one of these categories.

The previous behavior was too binary: the interface either showed all data or hid it completely. Expert Soft adjusted it to support partial visibility based on the user’s permissions.

The updated behavior included:

Users with the required permissions saw the complete financial dataset.
Users with partial access saw only the most recent annual period, with a banner explaining the restriction.
Web Component permissions controlled which interface elements were rendered for each user.

The implementation focused on interpreting existing permission signals and applying them correctly in the interface. Data collection and storage mechanisms remained unchanged, which allowed the team to improve access control without disrupting the underlying financial data model.

Results

Independent delivery for the financial data area
The dedicated microfrontend allowed updates to be released without waiting for core website changes.
Lower coordination overhead
Clear ownership boundaries reduced dependency on unrelated platform teams.
New financial data capabilities for users
Risk Indicators became available through API endpoints and a dedicated interface.
Reliable alert delivery
The new financial data alert was integrated and verified across the existing notification flow.
More precise permission-based visibility
Users with partial access received clearer data visibility without storage changes.
01 / 02

Technologies

Java, MongoDB, Kafka, Microfrontends, Web Components, SendGrid, Python ETLs

Conclusion

Expert Soft helped the client create a more independent delivery path for the financial data area within a larger modular platform.

By separating the interface into a dedicated microfrontend, the team reduced release dependency and gained more control over domain-specific development. This setup then supported the rollout of Risk Indicators, financial data alerts, and more precise permission-based visibility without disrupting shared platform architecture.

Contact Us
All submitted information will be kept confidential
EKATERINA LAPCHANKA

EKATERINA LAPCHANKA

Chief Operating Officer