Enterprise Back-end System

There are several possible architectures available when designing an online insurance application. One approach is to have the web front-end implement both the website (for data capture) and all the associated business logic, product rules, workflows, and policies and data storage. However, for enterprise level solutions, usually an Enterprise Back-end System is already in place and connecting the website to the Enterprise Back-end System directly, in real-time, is compelling.

  • Usually, the Enterprise Back-end System is already in place and being used to run the daily business. It is undesirable to have to maintain and synchronise business rulesets in both the web front-end and the Enterprise Back-end System.
  • It is more straightforward to add a different type of front-end (website, mobile site, aggregator integration, desktop client), if required, when the back-end is already separated.
  • The back-end will usually be located on the Enterprise network and provides an additional security layer.
  • Processing is spread over multiple environments resulting in a better overall performance.
  • The back-end system may already exist in a legacy platform which is not suitable to be exposed on the web directly.

An Enterprise Back-end System essentially brings together many components described on this site into one powerful application:

Discover IT has developed and deployed applications using both approaches:

  • Stand-alone all-in-one solutions that contain all the items which would reside in both the front-end and back-end systems (Temporary Cover).
  • Front-end online applications that interact with existing back-end systems (MMA, Salaam Insurance).
  • Complete, separate, front-end and Enterprise Back-end Systems (FGOS - RSA Fyfe).
We're ready when you are. Let's talk.