eComp
Features
CLIENT
- Progressive Web Application
- Microsoft Identity Platform utilizing the open source Microsoft Authentication Library (MSAL)
- Responsive web design
- Aurelia JavaScript framework
- data management (change detection, undo, validation and processing)
- multi-lingual & globalization (currency, dates, justification)
- OData query support
- Typescript 4 static type-checking
SERVER
- Single sign-on, multi-factor authentication & passwordless options with Azure Active Directory
- Open source C# .NET 7.0 framework - optimal for lightweight microservices and containerized deployments
- Azure SQL
- JSON Web Token (JWT) validation & authorization
- Swagger framework integration for API development
Things have changed since FASAT was introduced...
What's an eComp?
eComp is a modern cloud based insurance compensation system designed to allow an easy upgrade path for existing FASAT/EIM clients.
Technology
eComp is written in C# .Net 7.0 with an Azure SQL database. The front end is web based and uses the Aurelia JavaScript framework with TypeScript. Deployments are containerized targeting Linux. Kubernetes is used for financial processing, reporting, security and audit services.
Security
eComp uses JSON Web Tokens (JWT) to securely send information from the Authentication server to the Application server. Access to data is protected with Transparent Data Encryption (TDE) for data at rest. Transport Layer Security (TLS) protects the data in transit and Always Encrypted protects designated Personally Identifiable Information (PII) making it unreadable to access outside of the application itself. The application uses role-based security which can be applied in layers with an optional personal layer that overrides the roles – this gives you the ease of using role-based security with enough flexibility to customize where required.
Privacy
Azure SQL has a data classification facility that the application uses to identify PII data which the security rules are applied against. Define security roles to restrict access to PII data except for those who have a need to know. Most people do not need to see personal details unless they are working directly with the client.
Cloud
eComp is built on Microsoft Azure – services utilized include Azure SQL, Application Service, Container Registry, Azure Kubernetes Service, Storage, Redis Cache, Azure Key Vault, Azure Service Bus, Application Insights, Cognitive Service, CDN & Azure DevOps. For Canadian carriers - Microsoft Azure has two Canadian data centers to address any future data residency issues.
Database
The application has one unified database unlike FASAT with the archive database which uses unions to combine the tables together. Azure SQL uses point-in-time restores (PITR) eliminating the need for backups. Also, optimization of data types and elimination of redundant fields results in a significantly smaller database.
Kubernetes
Elastic processing for background services and financial processing – allowing horizontal scaling by automatically increasing and decreasing the number of pods in a cluster depending on the volume of requests.
Multilingual
We use an open source JavaScript framework called I18next to provide multilingual capability for eComp. Currently there are 15 languages supported. The initial source data is Azure Microsoft Translator which can be updated to provide more exact translations. Fun Fact: FASAT used VBLM (VB Language Manager) to provide translations between English and French. It's from a company named WhippleWare owned by Ben Whipple – talked to him years ago when we implemented it – very interesting person.
Azure DevOps
eComp utilizes Azure DevOps - an integrated DevOps environment with Git repositories, continuous integration and delivery of the applications.
Development Utilities
A suite of utilities available to enhance development, testing, data conversion & gap analysis for projects - including data masking of existing data and data generation.