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.

Real-world applications are complex. They comprise many different parts that work together to accomplish a task. These parts can be challenging to understand and debug. Instrumentation, measuring, and logging are tools that can help you know how your application is performing and how it is being used.

Instrumentation is the process of adding code to your application to collect data about its execution. It is not a business feature but more like an 

 of any application. It is a clear candidate to have its own library and be shared among any feature.

 project, but eventually, this could be useful anywhere it could be published in public or private repositories. Let's start with the more generalistic and simple event entry data definition.

/**
 * An event raised during the application lifecycle.
 * @property level: The severity of the event.
 * @property message: The message explaining the event.
 * @property payload: Additional data.
 * @property source: The source (function, module...) of the event.
 * @property userId: The user ID associated with the event.
 * @property timestamp: The time the event occurred.
 */
export type AppEvent = {
  level: LogLevel;
  message: string;
  payload?: unknown;
  source?: string;
  userId?: string;
  timestamp: Date;
};

Measuring is the process of collecting data about the application's execution. This data can be used to monitor the application's performance and to understand how the application is being used.

So, the solution will expose an API to gather info from the application. The kind of info can be generic or concrete and evolve over time. For example, I would think about broad use cases, such as recording user events and metrics about the use of services.

---
title: Instrumentation measuring and logging
isPublicLesson: false
useMdx: true
---

# Instrumentation, measuring, and logging

Real-world applications are complex. They comprise many different parts that work together to accomplish a task. These parts can be challenging to understand and debug. Instrumentation, measuring, and logging are tools that can help you know how your application is performing and how it is being used.

## Instrumentation

Instrumentation is the process of adding code to your application to collect data about its execution. It is not a business feature but more like an _aspect_ of any application. It is a clear candidate to have its own library and be shared among any feature.

By now, I am only thinking of the _new-docs_ project, but eventually, this could be useful anywhere it could be published in public or private repositories. Let's start with the more generalistic and simple event entry data definition.

```typescript
/**
 * An event raised during the application lifecycle.
 * @property level: The severity of the event.
 * @property message: The message explaining the event.
 * @property payload: Additional data.
 * @property source: The source (function, module...) of the event.
 * @property userId: The user ID associated with the event.
 * @property timestamp: The time the event occurred.
 */
export type AppEvent = {
  level: LogLevel;
  message: string;
  payload?: unknown;
  source?: string;
  userId?: string;
  timestamp: Date;
};
```

## Measuring:

Measuring is the process of collecting data about the application's execution. This data can be used to monitor the application's performance and to understand how the application is being used.

So, the solution will expose an API to gather info from the application. The kind of info can be generic or concrete and evolve over time. For example, I would think about broad use cases, such as recording user events and metrics about the use of services.