How mehmetkirkoca/social-media-manager works
Main Components
A. Frontend Layer:
• Vue.js UI application (from the /ui directory)
• Nginx as reverse proxy/load balancer (nginx.conf present)
B. Microservices Layer:
• Gateway Service (services/gateway)
• Social Media Services:
• LinkedIn Service (services/linkedin)
• Twitter Service (services/twitter)
• Support Services:
• Socket Service (services/socket)
• Formatter Service (services/formatter)
• AI Grammar Correction Service (services/ai_grammar_correction)
C. Message Queue Layer:
• RabbitMQ (evidenced by RabbitMQConnector, Producer, and Listener in utils)
[Client Tier]
• ↓ ↑
[Service Tier]
• ↓ ↑
[Message Queue Tier]
Component Representation
• Rectangles with rounded corners for UI components (blue)
• Hexagons for microservices (green)
• Diamonds for external social media APIs (gray)
• Rectangles for utility services (orange)
Connection Flows
a) Client requests flow:
• Browser → Nginx → Gateway Service
• Gateway Service → Individual Microservices
b) Message queue interactions:
• Services → RabbitMQ → Consumers
c) External API connections:
• Social media services → External APIs
Key Elements to Highlight
a) Frontend Components:
• Vue.js application with main components (PostSender, NavBar, Footer)
• Nginx reverse proxy
b) Service Layer:
• Gateway service as the entry point
• Social media integration services
• Formatter and AI services for content processing
• WebSocket service for real-time features
c) Message Queue:
• RabbitMQ for inter-service communication
• Message flow patterns
Additional Details
Annotations for:
• API endpoints and protocols (REST, WebSocket)
• Data flow direction
• Service responsibilities
Technical Specifications
Important technical details:
• Node.js-based microservices
• Python for AI service
• Vue.js + TypeScript frontend
• Docker containerization
• RabbitMQ message broker
Remember to emphasize the scalability aspects and how the microservices architecture allows for independent deployment and scaling of each service. This is particularly important for a social media management platform that might need to handle varying loads across different services.