Mini social network
A learning application built in several versions to experiment with authentication, profiles, posts, and social relationships, with a backend that moved from Laravel to Java along the way.
- Status
- Completed
- Type
- Learning project
- Role
- Design and development with learning as the goal.
The initial problem
Understanding a full-stack system means connecting authentication, data, API, and interactions inside one coherent application.
Context
The project is a testing ground for technical evolution. It documents a progression and architecture changes rather than a finished product.
Objectives
- Practice a full-stack flow
- Compare several backends
- Understand user and content relationships
The solution
A deliberately small social network, rebuilt several times to compare framework and modeling choices.
Features
- Authentication
- Profiles
- Posts
- Interactions
- Comments
- Social relationships
Architecture
A full-stack architecture that went through several backend iterations, notably Laravel and then Java.
Technologies
Laravel · Java · REST API
Key decisions
- Reuse the same domain to compare approaches
- Keep the scope small
Challenges
- Evolving the model
- Comparing backend trade-offs
Learnings
- A rewrite only pays off when the comparison is explicit
Current state
The project is currently: completed. This reflects the state set in the administration area.
Next steps
- Document the differences between versions
Media