How yeshendradhaker/linkedin-app-microservices works
This README describes a LinkedIn-style microservices backend. The documented request path starts at a client, passes through a JWT-validating, rate-limiting API Gateway, and reaches user, post, feed, search, or notification services. Those services cover identity, content and media, cached feeds, full-text discovery, and notifications. The README also names MySQL, Redis, Elasticsearch, Kafka, and S3 as supporting state or infrastructure. The repository contains no source excerpts, so service-to-service calls and specific Kafka event producers are not established here.
Main entry points: README.md API Gateway
Components 12
Entry
- API Gateway
README.md
Core Services
- User Service
README.md - Post Service
README.md
Discovery and Engagement
- Feed Service
README.md - Search Service
README.md - Notification Service
README.md
State and Messaging
- MySQL
README.md - Redis
README.md - Elasticsearch
README.md - Kafka
README.md - AWS S3
README.md
Other components
- Client
Connections 13
- Client → API Gateway: sends requests
README.md - API Gateway → User Service: routes requests
README.md - API Gateway → Post Service: routes requests
README.md - API Gateway → Feed Service: routes requests
README.md - API Gateway → Search Service: routes requests
README.md - API Gateway → Notification Service: routes requests
README.md - User Service → MySQL: uses storage
README.md - Post Service → MySQL: uses storage
README.md - Post Service → AWS S3: stores media
README.md - Feed Service → Redis: caches feeds
README.md - Search Service → Elasticsearch: searches index
README.md - Notification Service → Kafka: consumes events
README.md - API Gateway → Redis: limits requests
README.md