Download Paper

First Name
Last Name
Job Title
I agree to the terms of Solace's privacy policy solace.com/privacy-policy/
Thank you!
Error - something went wrong!

A Guide to Connectivity for OpenFin Architects and Developers

OpenFin architects and developers need a way to seamlessly and securely interact with diverse data sources while preserving the agile OpenFin ethos. 

Architecting for reliable data access requires carefully considering your objective and needs.


In this paper, Thomas Kummumpurath, Solace's VP of Systems Engineering Amercias, outlines three architectural approaches architects and developers may choose to connect OpenFin applications to a variety of data sources: 


  1. Manage Connectivity in the OpenFin app. OpenFin allows you to connect directly to remote sources and can work if the number of endpoints is manageable and interactions are simple. 
  2. Construct bridges or gateways in the middle. Adding a middle layer allows you to uncouple your applications and substantially simplify OpenFin development. 
  3. Adopt a multi-protocol broker in the middle. If you want loose coupling and easier OpenFin development- and your data access is mission-critical-an enterprise-grade broker can harden the middle layer. 


Previous Flipbook
Event Mesh: Event-Driven Architecture for the Real Time Enterprise
Event Mesh: Event-Driven Architecture for the Real Time Enterprise

An analyst paper on how an event mesh can enable event-driven architecture and coexist with point-to-point ...

Next Flipbook
Cloud Migration for FSIs with OpenShift
Cloud Migration for FSIs with OpenShift