How deepak20001/blog-app-microservice works
Project Type & Purpose
• This is a full-stack, cross-platform mobile blog application following a microservice architecture.
• The Flutter “blog_client” handles UI, state management (BLoC), navigation, HTTP (Dio) and local storage.
• Three backend microservices handle domain logic:
• User Service (Node.js/TypeScript, MongoDB, Mongoose, JWT, Redis, RabbitMQ)
• Blog Service (Node.js/TypeScript, PostgreSQL, Redis, RabbitMQ, Google GenAI)
• Media Service (Go/Fiber, Cloudinary, JWT)
File Structure & Architectural Patterns
• blog_client/ – Flutter UI organized by core (services, theming, routing) and features (auth, blogs, profile, search, etc.) using the BLoC pattern.
• services/user/ – Express controllers, routes, middleware, models, utils, workers.
• services/blog/ – Same structure but uses PostgreSQL and AI endpoints.
• services/media/ – Go app with handlers and config; exposes HTTP endpoints for file uploads.
• Shared infra: each service uses environment variables, Redis for caching, RabbitMQ for event/async jobs.
Key Insights from README
• There is no API gateway; the Flutter client calls each service directly.
• Common external systems:
• MongoDB for user data
• PostgreSQL for blogs
• Redis for caching
• RabbitMQ for messaging between services (e.g., cache invalidation)
• Cloudinary for media storage
• Auth via JWT, passed in HTTP headers to backend.
Final Checklist
• External integration: Media Service → Cloudinary.
• JWT token flow from client to services.