Amazon Web Services –Migration Scenarios: Backend Processing Pipeline

Submitted by: Submitted by

Views: 292

Words: 1917

Pages: 8

Category: Business and Industry

Date Submitted: 11/09/2012 11:15 AM

Report This Essay

Amazon Web Services –Migration Scenarios: Backend Processing Pipeline Amazon Web Services –Migration Scenarios: Backend Processing Pipeline

October 2010

Migration Scenario: Migrating Backend Processing Pipeline to the AWS Cloud

Figure 1: Company C Architecture (Before Migration)

Use case

Company C is an automobile insurance claim processing company with an external-facing website from which claims are received and processed. A backend processing pipeline processes the claims by connecting to a complex workflow of third party services, legacy systems, content management systems (CMS), and reporting databases. The company maintains an internal back-office portal (Intranet) for Adjusters and Supervisors to manage the end-to-end workflow of processing claims.

Application Architecture

Incoming claims from the company’s website and various desktop clients are processed by the backend processing pipeline. See Figure 1 for an illustration of the current architecture. This pipeline consists of application servers that ingest the claims into a normalized relational database. Claims are then validated using the Rules Engine. The Rules Engine verifies and validates the data in the claims with the help from internal and external services like the 3rd party

Page 1 of 5

Amazon Web Services –Migration Scenarios: Backend Processing Pipeline

October 2010

Address Verification Service. Both the application server and Rules Engines are built using standard .NET technology. All the validated data is again stored in the same database which is backed up to tape drives periodically. Disputed claims undergo a complex workflow process and are processed using legacy systems. Undisputed claims are directly fed to the payments and billing system. The entire claims processing workflow is audited and logged in Reports DB running on MySQL DB, and central Claims DB using a SQL Server database. The company Intranet which is mainly used by Supervisors and Adjusters...