Recommender System Development: From Collaborative Filtering to Real-Time Serving
On one e-commerce project with a catalog of 300k SKUs, we boosted CTR from 1.8% to 4.4% — a 2.4x increase. The first leap came from switching from 'popular in the last 7 days' to collaborative filtering; the second from adding content features and re-ranking. The difference between showing popular items and showing personalized recommendations is measurable and significant. Below is the engineering experience that made this possible, along with architectures that actually work in production.
Collaborative Filtering: Matrix Factorization and Neural Approaches
Matrix Factorization is the classic approach for implicit feedback (clicks, views, purchases without explicit ratings). ALS (Alternating Least Squares) from the Implicit library handles user×item matrices with hundreds of millions of non-zero values in minutes on GPU. Latent factors 64–256, regularization λ=0.01–0.1 are starting parameters. Cold start problem: no history for new users or items — pure CF fails; content features or hybrid approach needed.
Neural Collaborative Filtering (NCF) replaces the dot product with a neural network. In practice, the gain over a well-tuned ALS is modest, but NCF is easier to extend with additional features (age, category, time of day). Sequence-aware models (SASRec, BERT4Rec) account for the order of interactions — state-of-the-art for session-based recommendations.
How to Choose Recommender System Architecture?
The answer depends on data, load, and cold start requirements. Below are three main approaches with selection criteria.
| Criterion | Collaborative Filtering | Content-Based Filtering | Hybrid (two-stage) |
|---|---|---|---|
| Data required | Interaction history | Item/user features | Both |
| Cold start | Poor | Works for new items | Partially solved |
| Diversity (long-tail) | Low, popularity bias | High | Medium–High |
| Serving latency | <5 ms (precomputed) | <10 ms (FAISS) | 20–50 ms |
| Implementation complexity | Low | Medium | High |
Hybrid architecture outperforms pure CF by 20–40% in long-tail coverage — validated on catalogs from 100k SKU.
Content-Based Filtering: When Interaction History is Scarce
Content-based recommends based on item characteristics rather than other users' behavior — solves cold start for new items. Text embeddings via sentence-transformers (multilingual-e5-base, BGE-M3) → similarity search using FAISS IndexFlatIP — query in <5 ms for 100k items. Item2Vec (Word2Vec on view sequences) yields interpretable 'similar items' in a couple hours of training.
Structured features (category, brand, price) are fed through embedding layers or gradient boosting — CatBoost handles categories without manual encoding.
Why Hybrid Models Work Better?
Production systems are almost always two-level. Stage 1 (Retrieval) — fast selection of 100–500 candidates from 300k items using ALS or Two-Tower model with vector search (FAISS, Qdrant). Stage 2 (Ranking) — heavy ranker on LightGBM or neural network with cross-features, time, device, and session context. LightFM is a good starting point for medium scale without heavy infrastructure. Our practice shows: moving from single-stage to two-stage yields a 15–25% accuracy improvement with only 20–30 ms additional latency.
Real-Time Serving: Architecture Under Load
Latency SLA — 50–100 ms at thousands of requests per second. Base recommendations precomputed (batch job hourly) → Redis by user_id → <5 ms. Real-time re-ranking via Kafka for events (clicks, cart adds) → update of context features. Feature serving — Redis with TTL (views in 24 hours, last clicked item). At 10k req/s, we deploy Redis Cluster with replication.
A/B testing is the only reliable way to measure improvements. Offline metrics do not always correlate with online. Kohavi et al., 'Online Controlled Experiments at Large Scale' (KDD 2013) — a must-read for the team. Test on 5–10% of traffic, monitor CTR, conversion, revenue per session. One of our client systems after hybridization increased revenue by 18% over a month of A/B.
Recommender System Development Timeline
The stages and typical time frames are in the table below. Costs are calculated individually based on catalog scale and latency requirements.
| Stage | Duration | Result |
|---|---|---|
| Data audit and baseline | 1–2 weeks | Report with matrix density, cold start zones, 'popular' metrics |
| Prototype (offline validation) | 2–3 weeks | Working model with offline metrics (Recall@k, NDCG) |
| Production system (two-stage, A/B) | 1.5–2.5 months | Low-latency service with monitoring and A/B infrastructure |
| Team training and documentation | 1–2 weeks | Model card, deployment runbook, fine-tuning session |
What's Included in Turnkey Development
- Data audit — user×item matrix density (typically <0.1%), activity distribution, temporal patterns, cold start statistics.
- Baseline — 'popular' as a simple threshold that is often hard to beat.
- Iterative improvement — ALS → content features → two-stage → sequence-aware. Each step with A/B.
- Serving infrastructure — batch precomputation, Redis, real-time re-ranking, Grafana monitoring.
- Documentation — model card with metrics, deployment instructions, feature descriptions.
- Team training — session on interpreting results and model fine-tuning.
- Support — 1 month post-launch (incident fixes, pipeline tuning).
We are a team with 7+ years of experience in recommender systems, having delivered over 30 projects for e-commerce and media. We guarantee transparent A/B testing and documented metric improvements.
Want to assess the growth potential of your catalog? Contact us for a free data audit. Order recommender system development — first prototype within two weeks.
Example ALS config for implicit feedback
from implicit.als import AlternatingLeastSquares
model = AlternatingLeastSquares(
factors=64,
regularization=0.05,
iterations=15,
use_gpu=True
)
model.fit(user_item_matrix)
More about the mathematics of recommender systems — in specialized literature.