Enable server-side caching with Redis and reduce the Current API Query Response Time 608ms to less than 1ms.

The following are the resources to reference for enabling Redis in the API:

• Redis Crash Course by web-dev-simplify
• Another Reference Vedio

Add award stats year wise.

Scarpe the award section of the player-stats and return that to the API.

Add Cluster Support for scalability of the server.

• use node-js cluster module to create distribution over available clusters.
• use throng module to make scalability over the server on different workers.

Description
In the API root the navigation object topClubs has the wrong route, i.e api/v1/stats/top/players/:category.

To Reproduce
Steps to reproduce the behaviour:

1. Go to API-ROOT
2. See the topClub.route prop.
3. See the error

Expected behavior
topClubs.route should be api/v1/stats/top/clubs/:category.

What is category type?

Category type is my personal abbreviation to the names that have categories, currently i.e "players", "clubs".

Is your feature request related to a problem? Please describe.
When working with a client we have to hardcode the category type as a list.

Describe the solution you'd like
Create a new API route that will return an array of the category types.

Description

Merge the TopPlayer Controllers to a single file to avoid code repetition.

Add top-clubs stats in different categories.

Add clubs stats with rank and their stats in different categories.

Add all top player categories on the PML.

Consider adding the routes of categories to the topPlayerCategory Array

Check if any modifications are required to the scraper.

The server is working fine in test and dev env but when NODE_ENV is set to production the server did not start up on the port.

Steps to reproduce the behaviour:

• cd in the project root directory
• run npm run build && npm start or NODE_ENV=production npm run dev
• Even after a long time the server didn't start up and log that the server has started.

Expected behaviour
The server should startup as in the NODE_ENV=devlopment and log to the terminal The server started on port 8080

Screenshots

• The server start in the NODE_ENV=development
  
  The server start in NODE_ENV=production
  Screenshot from 2021-09-19 20-07-10

Desktop (please complete the following information):

• OS: Linux/Ubuntu
• Browser: Chrome and Firefox
• Version: 20.04.3 LTS

Data Check of some unit-tests is returning an empty array.

To Reproduce
Steps to reproduce the behavior:

1. Go to root of the project.
2. Run yarn test.
3. Scroll down to scraper.test.ts test runs.
4. See error.

Expected behavior
The data check of clubs must return an array of type ClubData and it's length must not be equal to 0.

Log

● data check of fouls › should return 20 entries of players

    expect(received).toBe(expected) // Object.is equality

    Expected: true
    Received: false

      22 |         it("should return 20 entries of players", async () => {
      23 |             const clubData: ClubData[] = await scrapeClubData(data);
    > 24 |             expect(clubData.length > 0).toBe<boolean>(true);
         |                                         ^
      25 |         });
      26 |     });
      27 | }

      at test/scraper.test.ts:24:41
      at fulfilled (test/scraper.test.ts:5:58)

How to fix

• Check if those categories exits.
• Check if the pml website have the data for those categories.
• Check the return of those categories on the API.