How d3rrickla/fortunelink works
Project type and purpose
• This is a monolithic backend service (a Java Spring Boot application) that powers FortuneLink—a social and personal-finance platform.
• Its purpose is to expose RESTful APIs for user management, social “community” features, financial “goals” tracking, and “portfolio” management.
File structure
• Top-level “backend/fortunelink” directory contains a standard Maven/Spring Boot layout:
• pom.xml – project dependencies & build
• src/main/java/com/laderrco/fortunelink – application code
• src/main/resources/application.properties – configuration
• src/test/java/… – automated tests
README
• Very brief: “A social and personal finance platform for people tired of not knowing.”
• Confirms focus on social (community) + personal finance (goals, portfolio).
Main components
a. External clients
• Web UI (SPA)
• Mobile App
b. API layer
• Spring Boot RestControllers
• API Gateway or Load Balancer (optional)
c. Service layer
• Business logic components (CommunityService, GoalsService, PortfolioService)
d. Persistence layer
• Repositories (JPA interfaces)
• Relational Database (PostgreSQL/MySQL/H2)
e. External integrations
• Authentication provider (e.g. OAuth2 / Keycloak / Firebase Auth)
• Financial-data aggregator (e.g. Plaid, Yodlee)
• Email/SMS notification service
Relationships and interactions
• Clients → (HTTPS) → API Gateway/Load Balancer → Spring Boot Controllers
• Controllers → Service Layer → Repositories → Database
• Services ↔ External APIs (auth, financial data, notifications)
Architectural patterns & design principles
• Layered architecture (Controller → Service → Repository)
• Configuration-as-code (application.properties) and test coverage via src/test.
Technologies & frameworks
• Java 17+
• Spring Boot starter-web, starter-data-jpa
• Maven build (mvnw wrapper)
• Relational Database (PostgreSQL/MySQL/H2)
• (Optional) OAuth2 / JWT for security
• External SDKs for financial integration