Case study · Database Systems
Freelance Marketplace Database
Relational database · Coursework
A relational database design for a freelance marketplace, with normalized entities and SQL-side business logic.
01 / Context
The problem
A marketplace has connected workflows for accounts, skills, projects, bids, and payments. The schema needs to represent these relationships while limiting duplication and preserving integrity.
My role: Academic database project; source files document schema and SQL features.
02 / Implementation
How it works
01Model relationships
Separate entity responsibilities and represent relationships explicitly, including skills and project participation.
02Enforce integrity
Use keys and constraints to keep records consistent, and SQL-side features to package recurring operations.
Implementation highlights
- Marketplace entities for users, freelancers, clients, projects, bids, and payments
- Schema design and normalization work
- SQL views and procedural database features documented in the repository
03 / Evidence
What can be verified
The points below summarize the public repository and owner-provided CV where noted. Read the source for implementation details and the evaluation setup before drawing further conclusions.
MySQL project repository.
04 / Boundaries
Limitations and next questions
- This is a database coursework project rather than a deployed commercial marketplace.
- Operational security, payment compliance, and production scale are outside the demonstrated scope.