Register
Submit a solution
The challenge is finished.

Challenge Overview

Challenge Summary

Welcome to the “Billing Rate - Rate File Processor Challenge” challenge! The goal of this challenge is to create a Node JS based AWS Batch Job which will process the rate inquiry file and produce the results.

NOTE: Please be careful of the timeline phases. Every phase is shortened.

Project Overview

Our client wants to build a tool that has the capability to calculate & view rates for a given population of contracts within specified groups or lists of members. 

  • For this, we have developed a frontend application from where users can upload the rate inquiry request. 
  • This request is saved in AWS S3 as a CSV file(which we will call input file) in the “/rate-inquiry/input” directory. 
  • This input file will be processed by a service running on the AWS batch job(which we will call rate file processor). 
  • The rate file processor will consume the existing client’s API and prepare the result. 
  • The processor will save the result into another AWS S3 directory “/rate-inquiry/results/”. 
  • The result can be either successful or failure. If the result is successful then the result file format will be .csv else .err file. 
  • This results file will be accessible to the user through the frontend app.

So far, we have developed the frontend prototype and backend rest API for the app. Now in this challenge, we will be developing the “rate file processor”.

Technology Stack

Node.js 12.x, Typescript, AWS 

Assets

The following items are shared on the forum

  • Swagger and mock API of Client’s existing API which this job will consume to prepare the results.

Individual requirements

1. Create rate file processor AWS batch job
  • You will prepare the AWS cloud watch to trigger the AWS batch job
  • Create AWS batch job to process the input files
  • The job processing detail is shared on the forum.

IMPORTANT NOTES:

  • Please ensure that you are following best practices of Node JS and AWS Batch Job development 

  • No lint errors in API code.

  • Unit tests are required with a minimum of 90% coverage

  • Unit tests should be done each method independently, please mock external dependencies 

  • If you have any doubts, Please feel free to post it in the forum. We will be happy to resolve your queries as soon as possible.



Final Submission Guidelines

Please submit the zip file containing:

  • Guide to setup the Job including other required setups to deploy in above architecture
  • AWS batch job source code with detailed README and unit tests

ELIGIBLE EVENTS:

2020 Topcoder(R) Open

Review style

Final Review

Community Review Board

Approval

User Sign-Off

ID: 30129620