Why should you care?

Leaders need near-real-time metrics without analysts running manual Mongo queries.

See it live — copy this example

Paste into your MeanVerse project (Angular + Express + MongoDB), then run with ng serve / node / mongosh as noted.

// meanverse-analytics/
//   api/src/routes/metrics.routes.ts
//   web/src/app/features/analytics/metrics.service.ts

router.get('/metrics/mrr', auth, requirePermission('analytics:read'), async (req, res, next) => {
  try {
    const mrr = await Invoice.aggregate([
      { $match: { tenantId: req.user.tenantId, status: 'paid', periodStart: { $gte: startOfMonth() } } },
      { $group: { _id: null, mrrCents: { $sum: '$amountCents' } } }
    ]);
    res.json({ mrrCents: mrr[0]?.mrrCents ?? 0 });
  } catch (e) { next(e); }
});

@Injectable({ providedIn: 'root' })
export class MetricsService {
  private http = inject(HttpClient);
  mrr() { return this.http.get<{ mrrCents: number }>('/api/analytics/metrics/mrr'); }
}

What happened?

• Aggregation computes MRR server-side — browser never sees raw invoice rows.
• MetricsService feeds Angular chart component.
• Permission protects financial data.

Practice next

1. Define metric endpoints backed by aggregation pipelines.
2. Cache expensive aggregates in Redis 5 min TTL.
3. Angular dashboard with date range filter signal.
4. Add comparison param ?compare=previousMonth.
5. Schedule nightly materialized metrics collection.

Remember

Analytics = Mongo aggregate + Angular charts. Compute KPIs on server. RBAC on sensitive financial metrics.

SaaS board meeting

CEO opens MeanVerse analytics Monday 8am for weekly MRR.

Outcome: Cached aggregation loads in 200ms; board trusts single source.