Scribd
Upload
23 views1 page

Microservices Architecture

The document outlines a microservices architecture focusing on various components such as Authorization, Background Information, Course Specific Information, Learner Prompts, and Decision Tree. Each component includes its purpose, content, database type (primarily relational), and technology stack. The architecture aims to enhance user experience by tailoring learning paths based on user data and interactions.

Uploaded by

Shlok Sand
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
23 views1 page

Microservices Architecture

The document outlines a microservices architecture focusing on various components such as Authorization, Background Information, Course Specific Information, Learner Prompts, and Decision Tree. Each component includes its purpose, content, database type (primarily relational), and technology stack. The architecture aims to enhance user experience by tailoring learning paths based on user data and interactions.

Uploaded by

Shlok Sand
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd

Microservices Architecture

1.​Authorization:
a.​ Purpose: Login for everyone
b.​ Content: Basic
c.​ DB: Relational
d.​ Tech Stack: -​

2.​Background Information:
a.​ Purpose: Happens at the start (first login), gives us a basic learner
overview
b.​ Content: Demographics, Content preferences, Learning Style, General
Skill Level (also includes writing style, attention span)
c.​ DB: Relational
d.​ Tech Stack: -​

3.​Course Specific Information:


a.​ Purpose: user reported for a particular course, where they are rn and
where they wanna reach
b.​ Content: Learner Course Objective Check, Learner Level, Prerequisite
Mastery Check, Learner Skills Check, Diagnostic Assessment,
Tracking User Patterns and Trends
c.​ DB: Relational
d.​ Tech Stack: sme​

4.​Learner Prompts:
a.​ Purpose: Store what the learner asks the sme and the sme’s output
b.​ Content: User, Prompt, Answer, Sequence
c.​ DB: Relational, NoSQL
d.​ Tech Stack: sme​

5.​Decision Tree:
a.​ Purpose: Inferences based on attributes of which content to pull out
b.​ Content: todo
c.​ DB: todo
d.​ Tech Stack: todo

You might also like