How arjunhg/servicemeshx works
Project type and purpose
• This is a full-blown Node.js microservices application.
• It implements a microservices architecture with an API Gateway at the front, four independent services (Identity, Post, Media, Search), and shared infrastructure (MongoDB, Redis, RabbitMQ).
• Purpose: handle authentication, content creation, media management, and full-text search in a scalable, event-driven manner.
File structure
• Top-level:
• api-gateway/
• identity-service/
• post-service/
• media-service/
• search-service/
• docker-compose.yml
• Each service:
• Dockerfile + Readme + package.json
• src/
– controllers, routes, middleware, models (where applicable), utils, server.js
– Event handlers in media and search for RabbitMQ integration
• Shared infra inferred by docker-compose.yml: MongoDB, Redis, RabbitMQ.
README for additional insights
• Tech stack: Node.js, Express, MongoDB, Redis, RabbitMQ, Docker, Winston, Cloudinary.
• Architecture patterns: API Gateway, event-driven communication via RabbitMQ, caching via Redis, JWT auth via Identity service.
Detail without overthinking
• Every microservice component, its data store, and its event/HTTP interactions
• Middleware roles (auth, error-handling) in the gateway and services