From the course: Build Modern Web Apps with React, Hooks, State Management, and APIs Using Vite or Next.js

Unlock this course with a free trial

Join today to access over 25,200 courses taught by industry experts.

Feature-first/domain-driven

Feature-first/domain-driven

From the course: Build Modern Web Apps with React, Hooks, State Management, and APIs Using Vite or Next.js

Start my 1-month free trial Buy for my team

Feature-first/domain-driven

“

Welcome back. In the previous video, we named three architecture approaches. Feature First, Atomic Design, and Layered. Please be aware that there can be more approaches you can hear which might be a combination of these three or a new one. But these three are the most commonly used and can be considered as the go-to approaches based on your use case. Let's discuss each of them in detail. Feature first, which is also known as domain driven approach, is used when we want our app scaled around business features or domains. As I explained in the previous videos, we usually have team handling part of a bigger project. So, this approach works best. Each folder is isolated having its own common folder structure for components, styles etc. This is how a feature-first approach codebase design looks like. Over here in the source folder, you have a features folder which has multiple subfolders for all the features. For example, authentication, dashboard and inventory etc. Look closely that in…

Contents