How ahmadexe/prism-backend works
Project type and purpose
• PRISM is a backend‐centric, decentralized social‐media platform implemented as a suite of microservices.
• Its goal (per README) is to give users full control of their data via blockchain storage and to provide AI‐driven personalization without compromising privacy.
• The codebase shows four Go‐based services—auth, chats, jobs, posts—plus a gRPC definition for the auth service.
File structure
• Top‐level:
– grpc/auth: Protobuf definitions and generated Go stubs for the auth API
– services/{auth,chats,jobs,posts}: Four self‐contained microservices
• Each service follows a consistent layered layout:
– configs/: configuration loading
– data/: domain models
– handlers/: request handlers (business logic entry points)
– middlewares/: cross‐cutting concerns (e.g., authorization)
– repository|repositories/: persistence interfaces & implementations
– routes/: HTTP/gRPC route registration
– main.go: service bootstrap
• No frontend code here—this is strictly backend. External interactions include gRPC (auth) and likely HTTP REST for the other services.
README for additional insights
• Emphasizes blockchain for secure user data storage (an external component not directly in this repo)
• Mentions AI personalization (another external component or microservice)
• Includes a snippet on how to generate gRPC code for auth.