Developing Proactima Solutions' UX Risk Application, by using Azure Service Fabric
Published Feb 12 2019 02:26 PM 81 Views
First published on MSDN on Jan 20, 2017

Authored by Ed Price

Proactima Solutions lends their architecture to show us our 6th Service Fabric Customer Profile!

You can find all the Service Fabric Customer Profiles here:

Past profiles include Quorum Business Solutions , BMW , Schneider Electric , Mesh Systems , and TalkTalkTV .

I helped write and edit this latest article, which showcases the UXRisk application architecture. Find the full article here:

Back in 2008, Proactima Solutions set out to create a tool to capture their unique understanding of risk analytics and risk management. The first pilot from this effort was called Webrisk, despite having nothing to do with web . It was based on WPF and SQL Server and featured an on-premises installation and Click-Once deployment. Fast forward to 2011 and with the hire of a business developer and a solution architect, the formation of a cloud solution started.

Here are some of the top quotes from the article:

  • “Pushing out new revisions of code in Service Fabric is a core concept. This, combined with all the different upgrade policies, makes code rollout quick, easy and something we have confidence in.”–  Anders Østhus, , Proactima Solutions

  • “The local onebox Service Fabric experience is great. It’s not an emulation, it’s the actual bits running locally, and it allows us to debug 99% of our issues locally.”–  Anders Østhus

  • “Building microservices on Service Fabric makes it easier for our developers to reason about a piece of code. The SOLID principles can be implemented not just on code level, but also from an architectural level.”–  Jarle Nygård, Solution Architect, Proactima Solutions

  • “For a multitenant solution, scale is vital and with Service Fabric we can scale out as more tenants sign up. In fact, by creating services for each tenant we did not have to spend a lot of time thinking about the partitioning and sharding requirements let Service Fabric handle it for us.”–  Jarle Nygård

  • “Using the smart cache pattern for actors allowed us to reduce latency by orders of magnitude, compared to our previous implementation.”–  Jarle Nygård

  • “Knowing that Service Fabric is a distributed platform, I don’t have to worry about losing a node. I know that Service Fabric will rebalance itself, and continue running, so that I can fix it when I’m back at work.”–  Anders Østhus

Learn about their architecture here:

Keeping our heads in the cloud,

  • Ninja Ed

Version history
Last update:
‎Feb 12 2019 02:26 PM
Updated by: