educative.io

Detail Design diagram is wrong

Courses
,
#1

Hi ,

I feel the detail design diagram is wrong . You have mentioned the asynchronous queues to be between client and sync servers but the diagram is totally contradicting. Please correct it asap.

1 Like
#2

Thank you for reaching out to us. The author of the course will get back to you as soon as possible.

#3

Could you please help to address the below queries

  1. Why is the msg queue infra b/w metadata server and notification service. isn’t it supposed to be interacting with the client layer ?
  2. Why are there no arrows/ indications going from metadata servers into the metadata db
    .Everything is just going out of the metadata db .Nothing going into it?
    3.It would be nice to see a sequence of events depicting how the flow works, as in the steps showing the request response flow
#4

Also what is the blue cloud in the architecture diagram, NO LABELS. is this course even reviewed once/

#5

The blue cloud could be a DMZ VPC, because almost all LB of web server should stand after the public VPC for security concerns.

#6

The explanation is not in synch with the final diagram. Following video confirms that:

Correct flow seems to be:

  1. Upload is done first using a block upload service.
  2. Then changes are made to the metadata by metadata service.
  3. The metadata service then pushes changes to the notification service.
  4. Notification service takes a message and pushes it to the the other users(using socket or messaging queue).
  5. Notification service pushes it to the respective clients.

The points in explanation I feel are wrong or conflicting:

  1. message queue is client facing.
  2. client uploads go through notification service.
1 Like