ALU backend API rewrite
Budget: $2 – $8 USD
To have an auto-scale, redundancy, gracefully failed ALU backend system.
Scope of the project:
There are two possible project scope.
Option A, to rewrite the login related API to meet the objectives.
Option B, to rewrite the whole ALU backend API server code to meet the objectives.
In addition to the code rewrite, to deploy and launch on Azure instance(s) could be part of the project scope.
The new code should equip the capability to analyze and monitor user usage log trails across multiple servers, and have the ability to send alerts to dashboard and to mail list (maintained in DB) for any critical functional failure scenarios.
The new system should be able to ramp up processes / be redundant to meet demand and recover from any failure scenarios.
Deliverables & Acceptance Criterions:
For Option A, the deliverables and acceptance criterions are:
#1. Co-work with the current ALU backend API server code
#2. Co-work with current ALU/ALP firmware
#3. Pass unit test, integration test, user acceptance test, stress test, high availability and failover test
#4. Deploy and launch the rewritten code on Azure instance(s)
The new code could use the same programming language used in the existing backend system — Ruby, or another preferred language / development framework chosen by the 3rd party contractor.
For Option B, the deliverables and acceptance criterions are:
#1. Co-work with current ALU/ALP firmware
#2. Pass unit test, integration test, user acceptance test, stress test, high availability and failover test
#3. Deploy and launch the rewritten code on Azure instance(s)
The new code should be developed using the preferred language / development framework chosen by the 3rd party contractor. I’d rather not use Ruby and Ruby on Rails to rewrite the system, as the developers with these skills are relatively scarce in the job market.
3rd Party Skills Needed:
For Option A, the skills needed are:
#1. Ruby on Rails developers, familiar with AWS, Azure, scalability, high availability
Or
#2. Any other modern backend development framework, familiar with AWS, Azure, scalability, high availability
For Option B, the skills needed are developers familiar with any other modern backend development framework, AWS, Azure, scalability, and high availability.
What’s Next:
Decide to go Option A or Option B, or other options.
Source qualified Microsoft value-added partners.
Scope of the project:
There are two possible project scope.
Option A, to rewrite the login related API to meet the objectives.
Option B, to rewrite the whole ALU backend API server code to meet the objectives.
In addition to the code rewrite, to deploy and launch on Azure instance(s) could be part of the project scope.
The new code should equip the capability to analyze and monitor user usage log trails across multiple servers, and have the ability to send alerts to dashboard and to mail list (maintained in DB) for any critical functional failure scenarios.
The new system should be able to ramp up processes / be redundant to meet demand and recover from any failure scenarios.
Deliverables & Acceptance Criterions:
For Option A, the deliverables and acceptance criterions are:
#1. Co-work with the current ALU backend API server code
#2. Co-work with current ALU/ALP firmware
#3. Pass unit test, integration test, user acceptance test, stress test, high availability and failover test
#4. Deploy and launch the rewritten code on Azure instance(s)
The new code could use the same programming language used in the existing backend system — Ruby, or another preferred language / development framework chosen by the 3rd party contractor.
For Option B, the deliverables and acceptance criterions are:
#1. Co-work with current ALU/ALP firmware
#2. Pass unit test, integration test, user acceptance test, stress test, high availability and failover test
#3. Deploy and launch the rewritten code on Azure instance(s)
The new code should be developed using the preferred language / development framework chosen by the 3rd party contractor. I’d rather not use Ruby and Ruby on Rails to rewrite the system, as the developers with these skills are relatively scarce in the job market.
3rd Party Skills Needed:
For Option A, the skills needed are:
#1. Ruby on Rails developers, familiar with AWS, Azure, scalability, high availability
Or
#2. Any other modern backend development framework, familiar with AWS, Azure, scalability, high availability
For Option B, the skills needed are developers familiar with any other modern backend development framework, AWS, Azure, scalability, and high availability.
What’s Next:
Decide to go Option A or Option B, or other options.
Source qualified Microsoft value-added partners.