Skip to main content

Declarative Programming in Angular with Async Pipe and shareReplay

A declarative approach is a way that focuses on writing code that specifies what the application should do, rather than detailing how it should be done. For example, with the async pipe in Angular, we don’t need to write code to manually subscribe to an Observable, handle its data, and update the view. Instead, we simply specify in the template that we want the data from the Observable using the async pipe. Angular handles all the underlying processes to retrieve and display the data

It's often used in reactive programming with RxJS and Angular's built-in features, such as the async pipe.

export class ProductComponent {

  product$ = this.productService.getProduct();
  
  constructor(private productService: ProductService) {}
}

The product observable will hold the product data and the async pipe in the template will automatically subscribe and unsubscribe observable

<div *ngIf="product$ | async as product">
  <h1>{{ product.name }}</h1>
  <p>{{ product.description }}</p>
</div>

Benefit of declarative approach:

  • Reduces boilerplate code, making the codebase cleaner and more maintainable.
  • Automates state management, minimizing the risk of errors related to manual state management and keeping data in sync between components.
  • Improves performance through Angular's change detection strategy using OnPush, which triggers only when a component is marked as dirty.
  • Helps manage complexity in larger applications by keeping the codebase clean and modular.
shareReplay

To improve performance and network load we can cach the emissions from observables. Caching/storing data locally can:

  • Improve responsiveness
  • Reduce bandwidth and network consumption
  • Lower backend server load
  • Decrease redundant computations

One approach to cach the data is to use shareReplay(bufferSize?: number). 

ShareReplay is an operator in RxJS that caches and shares/replays the defined number of emissions subscribers. This is useful in situations where we want multiple subscribers to receive the same values without resubscribing to the source Observable or re-executing expensive operations.

      this.data$ = this.http.get('https://api.example.com/data').pipe(
        // Cache the response and share it with new subscribers
        shareReplay(1)
      );

bufferSize: This parameter specifies the maximum number of values to store in the buffer. When a new subscriber joins, it will receive the last bufferSize values emitted by the source observable. If not provided, the buffer size is unlimited.

Note: The location of the shareReplay operator is crucial. Before using shareReplay, all data processing happens prior to caching. However, once shareReplay is applied, the code below shareReplay is executed during each subscription.







Comments

Popular posts from this blog

Ensuring Data Integrity: The Role of Database Transactions

 1. What is database translation Database transactions are activities transferring, changing data from one consistent state to another consistent state for example in everyday life we make different kind of business transactions from buying products, changing or cancelling orders, buying tickets, etc. And all these activities involve the movement/transaction of data in the database. For example, consider a simple transaction of moving an amount of 5000 from one bank account to another. This transaction includes several steps: decrease the account balance by 5000, and then increase the other account balance by 50003. Each of these steps is a part of the transaction, and if any step fails, the entire transaction fails 2. Why it is crucial in reliable software systems? When it comes to business, whether it is personal or financial data, it is crucial to ensure the reliability and stability of data management. In our daily lives, we may frequently encounter errors related to database t...

The Developer’s Guide to Clean Code: Tips and Techniques

What is clean code? Clean code is a term used to describe code that is easy to read, understand, and maintain. It is written in a way that makes it simple, concise, and expressive. Clean code follows a set of conventions, standards, and practices that make it easy to read and follow. Here are some signs indicating that the code is not clean: 1. Poor names The name is not clear to understand, meaningless, or misleading . It doesn't reveal the intention of what it want to achieve. Consider the following examples: SqlDataReader drl; int od; void Button1_Click(); Class Pages1 In the examples above, it’s challenging to get the purpose of drl, od, or what Button1_Click() does. To enhance clarity, we can rename these identifiers as follows: SqlDataReader dataReader/reader; int overdueDays; void CheckAvailability_Click(); Class ViewCustomerPage {} Ambiguous names int? incidentNameId for instance. incidentNameId lacks clarity because if it represents the ID of an incident, then the inclu...

Maximizing Efficiency: The Power of Database Indexing

What is database performance? There are two main aspects of database performance: response time and throughput . Response time is the total time it takes to process a single query and returns result to the user. It's critical metrics because it directly impacts the user's experience, especially in applications where fast access to data is essential. The response time includes CPU time (complex queries will require more computational power and increase processing time), disk access, lock waits in multiple-user environment (more about database transaction ), network traffic. Throughput refers to how many translations the system can handle per second (TPS). A transaction could include different activities to retrieve and manipulate data. A single command like SELECT, INSERT, UPDATE, DELETE or a series of commands could be used to trigger these activities. If you’re running an e-commerce site, a single transaction might include checking the inventory, confirming the payment, and...