
Content Recommendation Engine — SASRec Sequential Recommender
Transformer-based sequential recommender with automated data pipelines, built as the IIT Ropar capstone project.
- SASRec transformer
- 98.47% AUC-ROC
- IIT Ropar capstone
What it had to solve
What someone wants next depends on the order of what they did before — a recommender that treats a user as an unordered bag of preferences throws that away. Sequence models keep it, but they only pay off if the data reaching them is clean and continuous, which makes the ingestion pipeline as much of the problem as the architecture.
The decisions that shaped it
A sequential model, deliberately
SASRec is a self-attentive sequential recommender: it uses attention over a user’s interaction history so that recent and contextually relevant actions carry more weight than old ones. That choice is what makes the model answer "what next" rather than "what similar".
Trained on TensorFlow at 25M parameters
The model is implemented and trained in TensorFlow against a 25M-parameter dataset, and evaluated on a held-out split — the 98.47% AUC-ROC figure is that evaluation, not training performance.
Automated ingestion rather than a fixed dump
Automated data pipelines feed the model instead of a one-off export. A sequential recommender degrades as soon as its view of recent history goes stale, so continuous ingestion is a correctness requirement, not an operational nicety.
Containerised and served, not left in a notebook
Docker packages the training and serving path and a Node.js service exposes it to a React client, which is the difference between a model that scored well and a system someone can call.
How the pieces sit together
- React front end consuming recommendations
- Node.js API serving the model
- SASRec self-attentive sequential recommender in TensorFlow
- Automated ingestion pipelines feeding training and inference
- Docker across the training and serving path
Built into the product
Sequence-aware recommendations
Attention over interaction history rather than static similarity.
Automated ingestion
Pipelines keeping the model’s view of history current.
Evaluated, not just trained
98.47% AUC-ROC measured on a held-out split.
Deployable
Containerised and served behind an API.
What it is built out of
- TensorFlow, SASRec, Python
- Node.js, React
- Docker
What it looks like






What it produced
- 98.47%
- AUC-ROC on the evaluation split
- 25M
- Parameter training dataset
- E2E
- Model through to served API