Facade service pattern in Angular

Introduction

The facade service pattern helps simplify complex code by hiding details behind a simple interface. It makes your Angular app easier to use and maintain.

When you want to hide complex logic from components.

When multiple services need to be combined into one simple service.

When you want to make your components cleaner and focused only on UI.

When you want to centralize data fetching and state management.

When you want to make testing easier by mocking one service instead of many.

Syntax

Angular

import { Injectable } from '@angular/core';

@Injectable({ providedIn: 'root' })
export class FacadeService {
  constructor(private serviceA: ServiceA, private serviceB: ServiceB) {}

  getData() {
    // combine or simplify calls
    return this.serviceA.getDataA();
  }

  saveData(data: any) {
    this.serviceB.saveDataB(data);
  }
}

The facade service is an Angular service decorated with @Injectable.

It uses dependency injection to get other services and exposes simpler methods.

Examples

A simple facade that wraps a user service method.

Angular

export class UserFacade {
  constructor(private userService: UserService) {}

  getUser() {
    return this.userService.fetchUser();
  }
}

This facade combines two services to simplify product and cart actions.

Angular

export class ProductFacade {
  constructor(private productService: ProductService, private cartService: CartService) {}

  getProducts() {
    return this.productService.getAll();
  }

  addToCart(productId: string) {
    this.cartService.add(productId);
  }
}

Sample Program

This example shows a facade service that hides two services: one for data and one for logging. The component uses only the facade to get data and log actions.

Angular

import { Injectable } from '@angular/core';

@Injectable({ providedIn: 'root' })
export class DataService {
  getData() {
    return 'Data from DataService';
  }
}

@Injectable({ providedIn: 'root' })
export class LoggerService {
  log(message: string) {
    console.log('Log:', message);
  }
}

@Injectable({ providedIn: 'root' })
export class FacadeService {
  constructor(private dataService: DataService, private loggerService: LoggerService) {}

  fetchData() {
    this.loggerService.log('Fetching data');
    return this.dataService.getData();
  }
}

// Usage in a component
import { Component } from '@angular/core';
import { FacadeService } from './facade.service';

@Component({
  selector: 'app-root',
  template: `<h1>{{ data }}</h1>`
})
export class AppComponent {
  data = '';

  constructor(private facade: FacadeService) {
    this.data = this.facade.fetchData();
  }
}

Important Notes

Facade services keep your components simple and focused on displaying data.

They help reduce repeated code by centralizing logic.

Use facades to improve testability by mocking one service instead of many.

Summary

The facade service pattern hides complex service logic behind simple methods.

It makes Angular components cleaner and easier to maintain.

Use it to combine multiple services and centralize data handling.

Practice

1.

What is the main purpose of using a Facade Service in Angular?

easy

A. To directly manipulate the DOM from services

B. To replace Angular modules with a single service

C. To simplify component code by hiding complex service logic behind simple methods

D. To create multiple instances of services for each component

Solution

1. Step 1: Understand the role of Facade Service

   A Facade Service acts as a simple interface hiding complex logic from components.

2. Step 2: Identify the benefit in Angular components

   This pattern keeps components clean and easier to maintain by centralizing service calls.

3. Final Answer:

   To simplify component code by hiding complex service logic behind simple methods -> Option C

4. Quick Check:

   Facade Service purpose = Simplify logic [OK]

Hint: Facade hides complexity behind simple methods [OK]

Common Mistakes:

• Thinking Facade replaces Angular modules
• Believing Facade manipulates DOM directly
• Assuming Facade creates multiple service instances

2.

Which of the following is the correct way to inject a facade service MyFacadeService into an Angular component constructor?

easy

A. constructor(private myFacadeService: MyFacadeService) {}

B. constructor(public MyFacadeService) {}

C. constructor(myFacadeService: new MyFacadeService()) {}

D. constructor(private myFacadeService = MyFacadeService) {}

Solution

1. Step 1: Recall Angular dependency injection syntax

   Angular injects services via constructor parameters with access modifiers and type annotations.

2. Step 2: Match correct syntax

   constructor(private myFacadeService: MyFacadeService) {} uses private and type MyFacadeService, which is correct.

3. Final Answer:

   constructor(private myFacadeService: MyFacadeService) {} -> Option A

4. Quick Check:

   Inject service with private + type [OK]

Hint: Use private and type in constructor for injection [OK]

Common Mistakes:

• Omitting access modifier (private/public)
• Using new keyword inside constructor parameters
• Assigning service without type annotation

3.

Given this facade service method:

getUserName(): Observable<string> {
  return this.userService.getUser().pipe(
    map(user => user.name)
  );
}

What will the component receive when subscribing to getUserName()?

medium

A. A synchronous string value of the user's name

B. An observable emitting the entire user object

C. A promise resolving to the user's name

D. An observable emitting the user's name as a string

Solution

1. Step 1: Analyze the facade method return type

   The method returns an Observable<string> by mapping the user object to user.name.

2. Step 2: Understand what subscribing receives

   Subscribing to this Observable emits the user's name string asynchronously.

3. Final Answer:

   An observable emitting the user's name as a string -> Option D

4. Quick Check:

   Facade returns Observable of user name [OK]

Hint: Facade returns Observable mapped to user name [OK]

Common Mistakes:

• Confusing Observable with Promise
• Expecting synchronous value instead of Observable
• Assuming entire user object is emitted

4.

Identify the error in this facade service method:

fetchData() {
  this.apiService.getData().subscribe(data => {
    this.data = data;
  });
  return this.data;
}

medium

A. Using arrow function inside subscribe is invalid syntax

B. Returns data before subscription completes, causing undefined result

C. Subscription should be inside component, not service

D. Missing return type annotation causes compile error

Solution

1. Step 1: Understand asynchronous subscription

   The subscribe callback runs later, so this.data is not set immediately.

2. Step 2: Identify return timing issue

   The method returns this.data immediately, likely undefined before data arrives.

3. Final Answer:

   Returns data before subscription completes, causing undefined result -> Option B

4. Quick Check:

   Async subscribe returns undefined early [OK]

Hint: Return inside subscribe or use Observable return [OK]

Common Mistakes:

• Returning data before async call finishes
• Thinking arrow functions are invalid in subscribe
• Believing subscription must be in component only

5.

You want to create a facade service that combines data from UserService and SettingsService and exposes a single observable userSettings$. Which approach correctly implements this?

class UserSettingsFacade {
  userSettings$: Observable<UserSettings>;

  constructor(private userService: UserService, private settingsService: SettingsService) {
    // Fill in here
  }
}

hard

A. this.userSettings$ = combineLatest([this.userService.getUser(), this.settingsService.getSettings()]).pipe(map(([user, settings]) => ({ user, settings })));

B. this.userSettings$ = this.userService.getUser().pipe(map(user => this.settingsService.getSettings()));

C. this.userSettings$ = this.userService.getUser() + this.settingsService.getSettings();

D. this.userSettings$ = forkJoin(this.userService.getUser(), this.settingsService.getSettings());

Solution

1. Step 1: Combine multiple observables correctly

   Use combineLatest to emit latest values from both observables together.

2. Step 2: Map combined values into single object

   Use map operator to create an object with user and settings properties.

3. Final Answer:

   this.userSettings$ = combineLatest([this.userService.getUser(), this.settingsService.getSettings()]).pipe(map(([user, settings]) => ({ user, settings }))); -> Option A

4. Quick Check:

   Use combineLatest + map to merge observables [OK]

Hint: Use combineLatest and map to merge observables [OK]

Common Mistakes:

• Using + operator to add observables
• Mapping one observable to another observable instead of values
• Using forkJoin which waits for all to complete once