---
# System prepended metadata

title: Group 24

---

# Group 24

- Comments with a:
    - :bulb: (bulb) are ameliorations
    - :question: (question) are questions
    - :warning: (warning) are misinterpretations that might lead to errors
    - :ok: are correct interpretations to express good work
    - :x: (incorrect) are issue in design that surely lead to an error

# :eyeglasses: Feedback of 1st deliverable

# Comments by criterion

## Code structure :neutral_face: (5)
- :bulb: Codebase is clean and documented.
- :question: "swamp" ?
- :question: testVersion\_logs-service folder ? Should be cleaner
- :ok: Microservices are independent and deployed with containers.
- :x: No scripts to deploy



## Documentation :heart_eyes: (10)
- :warning: Duplicate documentation, which one is the correct one?
- :ok: API well documented.

## Microservices :grinning: (8)
- :warning: Why is there another folder for the log service that containes Dockerfiles to build user_daemon and storage images?

## API :grinning: (6)
- :ok: API is level 2 and is consistent.
- :warning: Duplicate documentation, one is totally incorrect and the other is correct. (I picked the correct one, be carefull in further projects)

## State :heart_eyes: (4)
- :ok: User is saved in DB and can reconnect later on
- :bulb: Have to re-login when refreshing the page

## Logging service :neutral_face: (2)
- :x: Only used for auth service

## Elasticity :grinning: (6)
- :ok: Students improve the scalability policy by monitoring all services. Workload injection performed on cart, articles and users services.
- :warning: Can't reproduce


# :eyeglasses: Feedback of 2nd deliverable

# Comments by criterion

## Code structure :grinning: (8)
- :ok: Well documented
- :x: Mapping front-end to port 4000 while this port is not open by default
- :x: No deployment scripts
- :ok: Deployed on Azure.


## Documentation :heart_eyes: (5)
- :ok: Required information is there.
- :ok: Discusses changes from first deliverable.

## Logging service :disappointed: (1.5)
- :bulb: Only useful log is when a purchase is made

## Recommendation engine :neutral_face: (5)
- :bulb: Recommendations are computed on demand. A more optimized solution would compute recommendations periodically and save a result. The front end just retrieves the latest recommendation.
- :x: Too basic recommendation. Does not use the full power of M/R

## Frontend integration :disappointed: (2)
- :bulb: Only list top items sold without per-user recommendation

## Azure Blob :sob: (0)
- :x: No use of Azure Blob storage

---

# Group 25

---

# Group 27

- Comments with a:
    - :bulb: (bulb) are ameliorations
    - :question: (question) are questions
    - :warning: (warning) are misinterpretations that might lead to errors
    - :ok: are correct interpretations to express good work
    - :x: (incorrect) are issue in design that surely lead to an error

# :eyeglasses: Feedback of 1st deliverable

# Comments by criterion

## Code structure :heart_eyes: (10)
- :ok: Codebase is clean and documented.
- :ok: Microservices are independent and deployed with containers.
- :ok: Useful scripts to deploy
- :bulb: Should be able to change all the ENV variable with a single script 

## Documentation :heart_eyes: (10)
- :ok: Documentation clear and complete
- :ok: API well documented.

## Microservices :heart_eyes: (10)
- :ok: Each service documentation is well explained

## API :heart_eyes: (8)
- :ok: API is level 2 and is consistent.
- 
## State :heart_eyes: (4)
- :ok: User is saved in DB and can reconnect later on
- :bulb: Have to re-login when refreshing the page

## Logging service :heart_eyes: (5)
- :ok: The logging service has been well-designed and provides also a query API.

## Elasticity :heart_eyes: (8)
- :ok: Students improve the scalability policy by monitoring all services. Workload injection performed on cart, articles and users services.


# :eyeglasses: Feedback of 2nd deliverable

# Comments by criterion

## Code structure :heart_eyes: (10)
- :ok: Well documented
- :ok: Deployed on Azure.


## Documentation :heart_eyes: (5)
- :ok: Required information is there.
- :ok: Discusses changes from first deliverable.

## Logging service :heart_eyes: (5)
- :ok: Logging information is useful for the recommendation service. Different event types are logged and used by the recommender

## Recommendation engine :grinning: (8)
- :ok: There is a recommendation engine providing suggested items. The recommendations are also based on user events on its cart, allowing for more sophisticated queries.
- :warning: Recommendations are computed on demand. A more optmized solution would compute recommendations periodically and save a result. The front end just retrieves the latest recommendation.
- :bulb: No use of optimized M/R (rereduce)

## Frontend integration :heart_eyes: (10)
- :ok: Only list top items sold without per-user recommendation

## Azure Blob :heart_eyes: (5)
- :ok:  Images are stored in azure blobs.

---

# Group 28

- Comments with a:
    - :bulb: (bulb) are ameliorations
    - :question: (question) are questions
    - :warning: (warning) are misinterpretations that might lead to errors
    - :ok: are correct interpretations to express good work
    - :x: (incorrect) are issue in design that surely lead to an error

# :eyeglasses: Feedback of 1st deliverable

# Comments by criterion

## Code structure :neutral_face: (4)
- :bulb: Makefile for deployment
- :x: No usage of docker compose!!
- :question: How is your app working without network between microservices?



## Documentation :disappointed: (2)
- :x: Documentation is clearly missing loads of information and explaination.

## Microservices :neutral_face: (8)
- :warning: Roles are not described

## API :grinning: (2)
- :x: No description of the API even though the definitionS in the app.js files seem fine.

## State :heart_eyes: (4)
- :ok: User is saved in DB and can reconnect later on

## Logging service :sob: (0)
- :x: No logging service

## Elasticity :sob: (0)
- :x: No elasticity


# :eyeglasses: Feedback of 2nd deliverable

# Comments by criterion

## Code structure :neutral_face: (4)
- :x: No usage of docker compose!!
- :x: Not deployed on Azure.


## Documentation :disappointed: (1)
- :x: Almost non-existent

## Logging service :sob: (0)
- :x: No logging service

## Recommendation engine :sob: (0)
- :x: No recommendation

## Frontend integration :sob: (0)
- :x: No recommendation

## Azure Blob :sob: (0)
- :x: No use of Azure Blob storage

---


# Group 30

- Comments with a:
    - :bulb: (bulb) are ameliorations
    - :question: (question) are questions
    - :warning: (warning) are misinterpretations that might lead to errors
    - :ok: are correct interpretations to express good work
    - :x: (incorrect) are issue in design that surely lead to an error

# :eyeglasses: Feedback of 1st deliverable

# Comments by criterion

## Code structure :grinning: (8)
- :ok: Makefile for deployment
- :warning: No substitution script for DNS => has to be done manually
- :x: Images stored locally so swarm can't be used. Only manager can fetch images


## Documentation :neutral_face: (5)
- :x: Missing loads of information, screenshots, directives

## Microservices :grinning: (7)
- :ok: Each microservice has a clear role and it makes sense
- :x: Logging service missing
- :question: Why create 3 databases when one can do all the job?
- :x: Wrong justification of usage of 3 DBs

## API :disappointed: (2)
- :x: No description of the API
- :question: Catalog API seems midly complicated

## State :heart_eyes: (4)
- :ok: User is saved in DB and can reconnect later on

## Logging service :sob: (0)
- :x: No logging service

## Elasticity :neutral_face: (4)
- :x: Only the auth service is tested for scalability.
- :question: The artillery for the catalog is not necessary.
- :question: Why not test the Cart which is more important and subject to high load?

# :eyeglasses: Feedback of 2nd deliverable

# Comments by criterion

## Code structure :neutral_face: (5)
- :x: No prove of deployement on Azure. (Could not connect with ssh)
- :bulb: Deployement script with hardcoded VM IPs


## Documentation :heart_eyes: (5)
- :x: Almost non-existent

## Logging service :heart_eyes: (5)
- :x: No logging service

## Recommendation engine :neutral_face: (5)
- :ok: There is a recommendation engine providing suggested items.
- :x: Recommendations are computed on demand. A more optmized solution would compute recommendations periodically and save a result. The front end just retrieves the latest recommendation.
- :x: Wrong usage of M/R. You do all the computation on the Map phase and don't use the Reduce phase.

## Frontend integration :grinning: (8)
- :ok: Recommendation given as thumbnails

## Azure Blob :sob: (0)
- :x: No use of Azure Blob storage

---

# Group 33

- Comments with a:
    - :bulb: (bulb) are ameliorations
    - :question: (question) are questions
    - :warning: (warning) are misinterpretations that might lead to errors
    - :ok: are correct interpretations to express good work
    - :x: (incorrect) are issue in design that surely lead to an error

# :eyeglasses: Feedback of 1st deliverable

# Comments by criterion

## Code structure :grinning: (8)
- :ok: Makefile for deployment
- :warning: No substitution script for DNS => has to be done manually
- :x: Images stored locally so swarm can't be used. Only manager can fetch images


## Documentation :neutral_face: (5)
- :x: Missing loads of information, screenshots, directives

## Microservices :grinning: (7)
- :ok: Each microservice has a clear role and it makes sense
- :x: Logging service missing
- :question: Why create 3 databases when one can do all the job?
- :x: Wrong justification of usage of 3 DBs

## API :disappointed: (2)
- :x: No description of the API
- :question: Catalog API seems midly complicated

## State :heart_eyes: (4)
- :ok: User is saved in DB and can reconnect later on

## Logging service :sob: (0)
- :x: No logging service

## Elasticity :neutral_face: (4)
- :x: Only the auth service is tested for scalability.
- :question: The artillery for the catalog is not necessary.
- :question: Why not test the Cart which is more important and subject to high load?

# :eyeglasses: Feedback of 2nd deliverable

# Comments by criterion

## Code structure :neutral_face: (5)
- :x: No prove of deployement on Azure. (Could not connect with ssh)
- :bulb: Deployement script with hardcoded VM IPs


## Documentation :heart_eyes: (5)
- :x: Almost non-existent

## Logging service :heart_eyes: (5)
- :x: No logging service

## Recommendation engine :neutral_face: (5)
- :ok: There is a recommendation engine providing suggested items.
- :x: Recommendations are computed on demand. A more optmized solution would compute recommendations periodically and save a result. The front end just retrieves the latest recommendation.
- :x: Wrong usage of M/R. You do all the computation on the Map phase and don't use the Reduce phase.

## Frontend integration :grinning: (8)
- :ok: Recommendation given as thumbnails

## Azure Blob :sob: (0)
- :x: No use of Azure Blob storage

---


# Group 50

- Comments with a:
    - :bulb: (bulb) are ameliorations
    - :question: (question) are questions
    - :warning: (warning) are misinterpretations that might lead to errors
    - :ok: are correct interpretations to express good work
    - :x: (incorrect) are issue in design that surely lead to an error

# :eyeglasses: Feedback of 1st deliverable

# Comments by criterion

## Code structure :neutral_face: (6)
- :ok: Codebase is clean
- :ok: Microservices are independent and deployed with containers.
- :x: No deployment scripts


## Documentation :grinning: (8)
- :ok: There is a single document that gives a detailed overview about the deliverable.
- :warning: Some technological choices not detailed

## Microservices :heart_eyes: (10)
- :ok: Each microservice has a clear role and it makes sense

## API :grinning: (6)
- :ok: API is level 2 and is consistent.
- :x: No params description

## State :heart_eyes: (4)
- :ok: User is saved in DB and can reconnect later on

## Logging service :grinning: (4)
- :ok: The logging service has been well-designed and provides also a query API.

## Elasticity :neutral_face: (5)
- :ok: Students improve the scalability policy by monitoring all services.
- :x: No evidence of test 
- :warning: Code base not consistent

# :eyeglasses: Feedback of 2nd deliverable

# Comments by criterion

## Code structure :grinning: (8) +3 (Bonus)
- :warning: Manually change some variables
- :ok: Deployed on Azure.


## Documentation :grinning: (3)
- :x: No explaination of logs and recommendations

## Logging service :grinning: (3.5)
- :ok: Logging information is useful for the recommendation service. Different event types are logged and used by the recommender
- :warning: No explaination of what is logged

## Recommendation engine :grinning: (8)
- :ok: There is a recommendation engine providing suggested items.
- :x: Recommendations are computed on demand. A more optmized solution would compute recommendations periodically and save a result. The front end just retrieves the latest recommendation.

## Frontend integration :grinning: (8)
- :ok: Recommendation given as thumbnails

## Azure Blob :heart_eyes: (5) +2.5 (Bonus)
- :ok:  Images are stored in azure blobs.

---