https://khalilstemmler.com/articles/typescript-domain-driven-design/ddd-frontend/

Generally speaking, DDD communicates a number of powerful software organizational concepts, but they exist to address a problem with separating business, application, and presentation logic.

Since the frontend's entire purpose is, well, presentation, there are sections of DDD principles which do not apply.

For example, there are no entities in frontend, only value objects reflecting the behavior and contours of the domain object representations from the backend. There should also be no business logic in the frontend, in so far as possible.

Here are some ideas from DDD which I believe are powerful in any coding architecture:

• The use of SOLID principles
• Layered architecture, in which objects begin to take on the character of the real world behaviors they accomplish.
• Non-anemic architecture, but rather behavior, meaning, and domain coherence is communicated by objects, and not random if / else or switch statements.
• Ubiquitous Language
• Communicative and descriptive function naming, that illustrates the real-world connection to what the code is doing.