-
The diagram above is a visual representation of integrating all these architectures into a single actionable idea. As you can see, just doing the mental exercise of obeying these simple rules before coding a new system will save you a lot of headaches in the future. With this, if any of the technologies used in the system becomes obsolete (for example, the adopted web structure), you will be able to replace these elements without any problems. In practice, it's as simple as it sounds: by subdividing your project into layers you'll create a testable, readable, and easily optimizable system. In parallel, while defining the design layers in line with business rules and interface rules, it is essential to understand the relationship between application dependencies and entities.
- Single Responsibility Principle (SRP)
- Open Closed Principle (OCP)
- Liskov Substitution Principle (LSP)
- Interface Segregation Principle (ISP)
- Dependency Inversion Principle (DIP)
- Separation of Concerns (SOC)
- Don't Repeat Yourself (DRY)
- You Aren't Gonna Need It (YAGNI)
- Keep It Simple, Silly (KISS)
- Composition Over Inheritance
- Factory
- Adapter
- Composite
- Proxy
- Dependency Injection
- Abstract Server
- Composition Root
- Builder
- Singleton
- TDD
- Clean Architecture
- DDD
- Modular Design
- Dependency Diagrams
- Use Cases
- Fork this repository and clone it on your machine.
- Change the directory to
clean-architecture-apiwhere you cloned it.
- Install dependencies
$ npm install- Setup database
/* Create `.env` of the system */
$ cp .env.example .env
/* Run database with docker */
$ docker-compose up -d
/* Setting database, how create tables */
$ npm run prisma:push- Start the application
$ npm run dev- Open backend, the host localhost:3333
$ npm run test