Microservices reference
Production architecture with tracing
statuslive
stackFastify, RabbitMQ, Grafana Tempo
updated2026
DockerRabbitMQTempoLoki
01 / / the problem
Senior backend roles ask for microservices experience but most freelancers cannot demonstrate it. This is a real working system, not a diagram in a slide deck.
02 / / what i built
→Four independent services with isolated databases
→API gateway routing
→Event-driven communication via RabbitMQ
→Distributed tracing across all services
→Centralized logging with shared trace IDs
→End-to-end demo flow visible in trace UI
→Architecture documentation with decision rationale
03 / / how i built it
Fastify
Lower overhead than Express, better TS types
RabbitMQ
Mature message bus with proven reliability patterns
Grafana Tempo
Distributed tracing without per-span cost
Loki
Log aggregation that integrates with Tempo
04 / / live demo
→ open microservices.drodriguez.site
Demo data is seeded — poke at anything, it resets cleanly.
05 / / production extensions
Things deliberately out of scope for the demo, but I'd add for production:
→Service mesh (Istio or Linkerd)
→Saga pattern for distributed transactions
→Multi-region deployment
→Kubernetes orchestration