KO | EN

GitLite

Minimalist Open Source Repository Search Engine

gitlite — search

#dsh #dsh-plugin #developer-tools #ai-agent #claude-code #codex #typescript #ai-agents #deepseek-harness #mcp #cli #rust

laravel-ddd-salary

★ 23 Open GitHub ↗

Laravel API Server with DDD

// repository documentation

Was this content helpful?

★ 0 (0 ratings)

<h1 align="center">
  Laravel API with Domain-Driven Design (DDD)
</h1>

## 🚀 Current features
- User Domain basic CRUD
- SalaryHistory Domain basic CRUD
- Integration tests and Unit tests

## 📘 Introduction
I am learning to apply Domain-Driven Design (DDD) to Laravel, and this project is my first step. My goal is to build a standalone API server for salary management, which will be a part of my HRM (Human Resource Management) microservices architecture.

That's why this repository does not include any authentication functionality. There are a few parts of the code where I simulate a logged-in user to test the authorization service -- please ignore this for now. I plan to implement a JWT middleware later, which will handle the authentication

Some of my inspirations have been these remarkable articles:
- https://github.com/Orphail/laravel-ddd
- https://www.hibit.dev/posts/43/domain-driven-design-with-laravel-9
- https://martinjoo.dev/blog

I primarily started by following Dani Martinez's Orphail repository, which has been a great help in visualizing how Domain-Driven Design (DDD) should be implemented.
Howerver, I have made a few changes to the folder structure and incorporated additional elements that I believe will be more useful in a real-world context.

And lastly, I would really appreciate any advice on how to improve this project, even if it's about the smallest issues, coding conventions, or areas where I'm not following best practices. I want to learn and improve, so all feedback is valuable to me.

If you find this repo useful, please give me a star or an encouraging comment, I would really appreciate it.

You can contact me via

Email: vinh0809it@gmail.com

Facebook: https://www.facebook.com/vinh0809it/

## 📗 Installation
1. ```composer install```
2. ```cp .env.example .env```
3. ```php artisan key:generate```
4. Set database connection in the ```.env```
5. ```php artisan migrate```
6. ```php artisan db:seed```
7. ```php artisan test```
8. ```php artisan serve```

9. Import the Postman JSON file located in the 'postman' folder to have the API collection

## 📁 Structure particularities

I find this structure clearer, so I decided to stick with it.
For more information, you could visit Orphail repository.

User domain is just a mocked example
You could focus on the SalaryHistory Domain, that follows more strict with DDD principles than User Domain

```
├── User
│   ├── Domain
│   ├── Application
│   ├── Presentation
│   └── Infrastructure
├── SalaryHistory
│   ├── Domain
│   ├── Application
│   ├── Presentation
│   └── Infrastructure
```

laravel-ddd-salary

Explore Similar Repositories

Was this content helpful?

Recent Feedback

Download README