nikolaiunknown/socialmedia

Purpose and Runtime

SocialMedia is a containerized Java 23/Spring Boot backend for social networking: identity, profiles, friendship, posts/images/likes, user search, and real-time chat. The application entry point is src/main/java/com/media/socialmedia/SocialMediaApplication.java; HTTP APIs, static assets, and Swagger/OpenAPI are served by the Spring process.

• src/main/resources/static/api-docs.yaml

• Dockerfile

• docker-compose.yaml

API and Application Boundary

REST controllers are the external HTTP boundary. They accept request DTOs, invoke domain services, and return response DTOs. Major endpoint groups cover authentication, profiles/social graph, posts/media, administration, search, and chat. ChatHandler is a separate real-time message ingress alongside conventional controllers.

• src/main/java/com/media/socialmedia/Controllers/AuthController.java

• src/main/java/com/media/socialmedia/Controllers/PostController.java

• src/main/java/com/media/socialmedia/Controllers/ChatHandler.java

Authentication and Authorization

Registration and login flow through registration/user services and issue JWT access tokens plus refresh-token state. Refresh tokens are persisted and exposed through an HTTP-only cookie. Spring Security config and a token filter establish authenticated request context; authorization distinguishes Admin and regular users.

• src/main/java/com/media/socialmedia/Configs/SecurityConfig.java

• src/main/java/com/media/socialmedia/Security/TokenFilter.java

• src/main/java/com/media/socialmedia/Services/RefreshTokenService.java

Core Social Domain

JPA entities model durable users, posts, chats/messages, and refresh tokens. Services implement higher-level social operations: profile changes, friend invitations/relationships, blacklist enforcement, likes, posts, and admin actions. Controllers should not directly own persistence logic; repositories form the relational persistence boundary.

• src/main/java/com/media/socialmedia/Entity/User.java

• src/main/java/com/media/socialmedia/Entity/Post.java

• src/main/java/com/media/socialmedia/Services/FriendService.java

Chat and WebSocket Flow

WebSocket/STOMP configuration exposes real-time chat transport. Incoming messages are handled through chat-facing controller/handler code, then chat services validate access/blacklist conditions, apply the stated per-user Bucket4J rate limit, persist chats/messages, and produce message DTOs. Chat access failures have domain-specific exceptions.

• src/main/java/com/media/socialmedia/Configs/WebSocketConfig.java

• src/main/java/com/media/socialmedia/Services/ChatService.java

• src/main/java/com/media/socialmedia/Entity/Message.java

Data, Cache, and Search Infrastructure

PostgreSQL is the system of record, initialized with schema SQL. Redis supports caching through a dedicated configuration/service layer. Elasticsearch holds UserSearchDocument records, queried through a separate search repository/service for RU/EN full-text user search. These are distinct storage concerns rather than interchangeable repositories.

• init/postgres/tables.sql

• src/main/java/com/media/socialmedia/Services/CacheService.java

• src/main/java/com/media/socialmedia/Services/SearchService.java

Media and Deployment

Image upload is handled at the HTTP layer and is intended for static serving from a Docker-mounted volume. Docker Compose runs four services: Spring backend, PostgreSQL 17, Redis 7.2.5, and Elasticsearch 7.17.28; Elasticsearch users are initialized from repository-provided data.

• src/main/java/com/media/socialmedia/Controllers/ImageController.java

• init/elasticsearch/users.json

• docker-compose.yaml