The complete guide to designing, developing, testing, and deploying enterprise applications with Angular

Angular Applications Architecture

Requirements and FAQs

Code style guide

Introduction

Start from the domain

Software architecture for Front-end

Domain, design, develop

Workspaces scenarios

Applications and Libraries

Mono repository multi project

Domain boundary with plain TypeScript

Application details with Angular

Presentational details with Angular

Domain boundary and application details

Testing big Angular solutions with ease

Narrow tests for business logic

Visual tests for the presentation layer

Wide tests for the user experience

Testing since the beginning

Configuration environment and tokens

Instrumentation measuring and logging

Security authentication and authorization

Core generic infrastructure

A library for your shared UI vocabulary

A set of basic atomic elements

Some generic composed blocks

User interface, a design system foundation

Reactive stores with Signals

API access as a commodity

Interceptors for the dirty job

Data stores, reactive access, and persistence

Features come in routes to pages

Anatomy of a Page control flow and services

Different levels of state management

Routes and pages

In this course we teach you how to design, develop, ane deploy enterprise level Angular Applications the right way. Despite the fact that Angular is an opinionated framework, specially suited to build large solutions, it requires a deep knowledge to take decisions at every step.

In almost 30 lessons we cover how to choose and use the correct tools, how to structure an application that scales and how to code some intricate solutions to common problems. It's a long course/book and comes with a complete working codebase fully tested.

It is taught by Alberto Basalo who has been working, advising, and training multinational corporations, banks, and public administrations in Angular for years.

The complete guide to design, develop, test, and deploy enterprise applications with Angular

How to design, develop and deploy big enterprise applications with Angular.

Best practices to organize your code in small reusable libraries.

Application of reactive flow patterns for better user and developer speed.

Leverage the latest Angular version features like stand-alone components.

Common functionality for any application ready to use.

During this book, we will build a real-world application. It will be a Google Docs clone with markdown edition capabilities and real-time HTML preview. Being a book about software architecture, we will focus on the business 

 which requires us to start our journey from 

Instead of delving into definitions and theoretical concepts. But, talking about the domain requires a minimum of understanding.

Fortunately, it is pretty easy to grasp the idea because it is what pays our bills. We write programs to solve business problems in a specific context. 

 is what we will call a domain. The domain model formally represents the technical solution, a set of 

 that defines the application data and behavior. 

So, domains are the starting point for software architecture because they define the needed solution. This lesson will show you how to prepare to solve business problems before writing Angular code.

If The Domain is the problem context, the domain 

. Depending on your background and your organization´s culture, you may come here after following a proper 

But when it comes to code, you will have many data models, validation rules, and business processes that you need to implement. We will materialize this in TypeScript artifacts such as 

classes, interfaces, types, and functions

. This set of code files will define the solution, and we will call it The Application's Domain Model.

Complex problems lead to complex solutions

 that are usually divided into more manageable 

. For example, a banking application may have a subdomain for customer management and another for account management...

 approach is an excellent way to organize your otherwise colossal domain. But it would help if you also properly managed the resulting pieces. For doing so, they are categorized into the 

The most basic building blocks of the domain model are the entities and the use cases. They are 

---
title: Start from the domain
isPublicLesson: true
---

# Start from the domain.

### What you will learn in this lesson.

During this book, we will build a real-world application. It will be a Google Docs clone with markdown edition capabilities and real-time HTML preview. Being a book about software architecture, we will focus on the business _problem_, not only on the Angular _solution,_ which requires us to start our journey from **the domain**.

Instead of delving into definitions and theoretical concepts. But, talking about the domain requires a minimum of understanding.

Fortunately, it is pretty easy to grasp the idea because it is what pays our bills. We write programs to solve business problems in a specific context. _The solution to those problems_ is what we will call a domain. The domain model formally represents the technical solution, a set of **entities and cases of use** that defines the application data and behavior. 

So, domains are the starting point for software architecture because they define the needed solution. This lesson will show you how to prepare to solve business problems before writing Angular code.

## The domain model.

If The Domain is the problem context, the domain _model_ is the **formal representation of that solution**. Depending on your background and your organization´s culture, you may come here after following a proper _domain-driven design_ (DDD) process, any _agile_ methodology, a traditional _requirements/analysis_ approach, or a combination.

But when it comes to code, you will have many data models, validation rules, and business processes that you need to implement. We will materialize this in TypeScript artifacts such as **classes, interfaces, types, and functions**. This set of code files will define the solution, and we will call it The Application's Domain Model.

### Domains and subdomains.

**Complex problems lead to complex solutions** that are usually divided into more manageable _subdomains_. For example, a banking application may have a subdomain for customer management and another for account management...

The _divide and conquer_ approach is an excellent way to organize your otherwise colossal domain. But it would help if you also properly managed the resulting pieces. For doing so, they are categorized into the **core, supporting, and generic subdomains**.

-   The **core** domain.: It is the one that generates the most **value** for your customers.
-   The **supporting** domains.: They are domains **necessary** to complete the operation of the core domain.
-   The **generic** domains.: Those domains you can find in any other application are **not specific** to your business. 

### Entities and use cases.

The most basic building blocks of the domain model are the entities and the use cases. They are _the nouns and verbs_ of the domain story.

-   **Entities** are data models filled with rules representing business objects—for example, a `User` entity with a `name` and an `email` property.
-   **Use cases** are the business processes that transform entities, **the verbs of the domain**—for example, `RegisterUser` or `AuthenticateUser`.