Community primitives
The code organizes posts, comments, likes, shares, profiles, and organization pages into dedicated features.
Backend / Campus community
Hoosier Hub
A campus community,
connected by design.
SYSTEM / HOOSIER-HUB01 → 04
01ClientsStudent experiences
02ControllersAuth, feed, posts, chat
03ServicesDomain behavior
04RepositoriesMongoDB documents
RESTapplication API
JWTauthentication layer
MongoDBdocument persistence
A REST API backend for an Indiana University social platform, connecting student profiles, posts, organizations, and conversations.
A community is more than a feed.
A campus community needs more than a feed. Profiles, organizations, conversations, and post interactions need a coherent backend with clear responsibilities.
A deliberate path through the problem.
Spring Boot controllers expose application features while services handle domain behavior and repositories manage MongoDB persistence. Separate models represent users, profiles, posts, pages, and messages.
JavaSpring BootMongoDBDockerMaven
The choices that shape the work.
Authentication at the boundary
JWT authentication and authorization filters sit alongside the application security configuration.
A repeatable delivery path
Docker, Maven, and GitHub workflows provide build, test, and deployment structure.
What the project delivers.
The public repository contains the backend foundation for a campus social network, including media services, search, feed APIs, and chat integration.
Boundaries make room for growth.
Clear controller, service, and repository boundaries make a growing social application easier to reason about as features multiply.