"Came up with following strategy:
take logs from user and send to LogService via API GW
LogService takes the responsibility of generating time based SequenceId and persist the log in NoSQL (DDB) with key as SequenceId as primary key and timein_millis as sort (secondary) key. There are many system design tutorials on generating sequential sequence id where prefix is current time in epoch (milliseconds)
Since there would be many LogService servers, spread across different availability zo"
Shahnawaz A. - "Came up with following strategy:
take logs from user and send to LogService via API GW
LogService takes the responsibility of generating time based SequenceId and persist the log in NoSQL (DDB) with key as SequenceId as primary key and timein_millis as sort (secondary) key. There are many system design tutorials on generating sequential sequence id where prefix is current time in epoch (milliseconds)
Since there would be many LogService servers, spread across different availability zo"See full answer
"I first clarified what he needed for the leaderboard meaning did he need a gaming leaderboard system, a stock market leaderboard system where the trades placed would be ranked in terms of values or a coding platform leaderboard where the users are ranked as per the points earned by solving the problem?
He answered that he wanted a multipurpose leaderboard system
He was specifically interested in the design of the api part
Explained him that assuming we had a flask api there would be a get re"
GalacticInterviewer - "I first clarified what he needed for the leaderboard meaning did he need a gaming leaderboard system, a stock market leaderboard system where the trades placed would be ranked in terms of values or a coding platform leaderboard where the users are ranked as per the points earned by solving the problem?
He answered that he wanted a multipurpose leaderboard system
He was specifically interested in the design of the api part
Explained him that assuming we had a flask api there would be a get re"See full answer
"Functional Requirement
Upload the file of any type
POST v1/drive
Upload the another version of file.
POST v1/drive/{fileId}
Delete the file.
DELETE v1/drive/{fileId}
Share the file.
POST v1/drive/{fileId}
Control the access level of the file.
Provide the file accessibility following the directory structure.
Non Functional Requirement
Reliability: The file along with its versions uploaded should be"
Vikash A. - "Functional Requirement
Upload the file of any type
POST v1/drive
Upload the another version of file.
POST v1/drive/{fileId}
Delete the file.
DELETE v1/drive/{fileId}
Share the file.
POST v1/drive/{fileId}
Control the access level of the file.
Provide the file accessibility following the directory structure.
Non Functional Requirement
Reliability: The file along with its versions uploaded should be"See full answer