Hi there! This is my entry to Origin's senior backend position assignment. The project was made using TypeScript and Node.js because they are the tools I work with daily and felt less insecure about using for the assignment.
I've tried taking a more domain driven approach, so you will notice that the HTTP server part of the solution was purposelly made to be very small. This allows us to easily test the solution without having to worry about the server itself and also allows us to easily add different kinds of applications in the future (such as a gRPC server or even a CLI) reusing great part of the existing code.
As far as the business logic goes, you will see that I have several InsuranceRiskCalculator classes (domain services), each one being concerned with calculating the risk score for a specific insurance line (auto, home, life or disability).
The core idea of the solution was implementing it in a way that all score changing logic (eg deducting 1 risk point if the user's income is above $200k) are contained in separate classes (which I called RiskFactors) that can be re-used and composed together with other RiskFactors (using the Chain of Responsibility pattern) to give the final risk score for a specific line of insurance. This makes the individual rules easier to test (although I've made the decision to test their combination in the InsuranceRiskCalculator classes instead of individually testing each rule) and removes duplicated logic, as one can simply combine multiple existing RiskFactors to calculate the risk score for a new insurance line.
I have also left some comments in the code itself, so feel free to check them out!
My main goal was translating the business requirements into tests as close as possible, so my approach was to first implement the test cases described in the assignment (eg "If the user is over 60 years old, she is ineligible for disability and life insurance.") and kinda build everything from there, by making sure those tests pass and then adding new specific tests as needed.
application: application services - used to glue together the domain services and entities and to serve as entypoints from the external world to our domaindomain: everything related to the domain (entities, domain services, etc)infrastructure: just contains a file meant to serve as a single point for all instances of the services used in the applicationserver: thin HTTP server that exposes our application services to the outside world
Make sure you have Docker installed
Build the image:
docker build -t awesome-assignment .Run:
docker run -p 3000:1337 -t awesome-assignment # you can change 3000 to any other port you have availableAfter the above steps a HTTP server will be running on port 3000 (or whatever port you chose)
The application exposes a single endpoint at / that receives a POST request and expects the same body as the one described in the assignment's README.
curl --location --request POST 'http://127.0.0.1:3000' \
--header 'Content-Type: application/json' \
--data-raw '{
"age": 35,
"dependents": 2,
"house": {"ownership_status": "owned"},
"income": 0,
"marital_status": "married",
"risk_questions": [0, 1, 0],
"vehicle": {"year": 2018}
}'Expected response (200):
{
"auto": "regular",
"home": "economic",
"life": "regular",
"disability": "inelegible"
}You can also run the tests using the same Docker image above:
docker run -t awesome-assignment npm testHope you like it!