Versions Compared

Version Old Version 3 New Version 4
Changes made by

Pradyumna Nagendra

Pradyumna Nagendra

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Info

  • The event is just a trigger to initiate the computation of the collection progress. The job uses DB and fetch the raw data to compute the progress.

  • When an assessment type content (Ex: QuestionSet) view ends, it is required to send the ASSESS events data in the request.

...

Once the view ends, the progress can be updated either synchronously or asynchronously

Progress Update: Sync

...

Pros:

  • There will no lag between viewer read and viewer summary.

  • No need of a separate sync process

Cons:

  • Updating multiple cassandra tables might have impact on performance with huge load

Progress Update: Async

...

Pros:

  • Can expect better performance as we update only user_content_consumption

Cons:

  • Expect a lag between viewer read and viewer summary responses.

  • Need a separate sync process on failure of the progress updates.

Content View Lifecycle:

When the user view the content in context of a collection and batch, for the first time its start, progress update and end triggers are processed. Revisit (2nd - nth view) of the content will be ignored to process and update the DB.

...