FINOS Plexus Interop · Open source

Connecting applications that were never built together

Financial workflows often span several independent applications. Plexus Interop provides a way for those applications to cooperate without requiring a single UI technology or a full rewrite.

My role Web architecture, implementation and delivery; historical FINOS contribution

01 / Context

The challenge

A user's workflow can cross tools written by different teams, with different frameworks and life cycles. Point-to-point integrations do not scale well as the number of applications grows.

02 / Contribution

What I did

Architected the web part of the interoperability approach and implemented its initial working foundation.
Built the communication patterns required to connect independent UI experiences.
Helped move the idea from a specific implementation into a reusable technology that could be adopted by other teams.

03 / Outcomes

What it enabled

Enabled more coherent workflows between otherwise separate applications.
The code was released as the FINOS Plexus Interop open-source project.
The upstream repository is now archived; this case study describes historical work, not current upstream maintenance.

04 / Takeaway

What I learned

Interoperability is most useful when teams retain ownership of their applications while users experience one connected workflow.