You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 5, 2025. It is now read-only.
Problem
The increasing velocity of business requirements as well external requirements like regulations require FinServ to be more agile in its adoption of new technologies and paradigms like cloud native. Financial services traditionally have been slow to adopt certain new technologies because of various enterprise challenges. Financial services organizations have also in the past been unable to collaborate and communicate with the community/industry at large regarding these requirements.
This has led to the following issue:
Vendors and open source haven't been aware of key FinServ requirements leading to FinServ being unable to adopt their products, projects, approaches and architectures
Proposed solution
A white paper detailing the general challenges that FinServ has in adoption of new technologies. This should also include an explanation of why we have some of the requirements we do and why we can't adopt certain technologies or patterns today without changes to our own approaches or changes to the technologies and patterns.
Creating this issue as a call to action to help out. Looking for additional contributors as well as general feedback on this approach. See the #fsug CNCF slack channel for more info around scheduling and synchronous collaboration on this.
Problem
The increasing velocity of business requirements as well external requirements like regulations require FinServ to be more agile in its adoption of new technologies and paradigms like cloud native. Financial services traditionally have been slow to adopt certain new technologies because of various enterprise challenges. Financial services organizations have also in the past been unable to collaborate and communicate with the community/industry at large regarding these requirements.
This has led to the following issue:
Proposed solution
A white paper detailing the general challenges that FinServ has in adoption of new technologies. This should also include an explanation of why we have some of the requirements we do and why we can't adopt certain technologies or patterns today without changes to our own approaches or changes to the technologies and patterns.
Creating this issue as a call to action to help out. Looking for additional contributors as well as general feedback on this approach. See the #fsug CNCF slack channel for more info around scheduling and synchronous collaboration on this.
Doc:
https://docs.google.com/document/d/1wBKQtibVlzybVXMASBwE6jGFWf9ea4CmR1bDLPf1DMg/edit
The text was updated successfully, but these errors were encountered: