Angular 18 Lazy Loading Guide: Traditional vs. Standalone Components

Рет қаралды 659

Learn Smart Coding

Күн бұрын

Пікірлер: 11

@helloworld7287 Ай бұрын

Thank you for the clear explanation, to-the-point discussion, and covering such an important topic.

@learnsmartcoding Ай бұрын

I appreciate the feedback! Keep watching all the upcoming upcoming videos.

@deadcxlm Ай бұрын

Hello! Could you please explain how, in DDD, business entities like Customer and Courier are related to User (the actual user of the application)? Since business entities do not store authentication information and only hold data for business logic, I’m still having trouble understanding this. :(

@learnsmartcoding Ай бұрын

Hi! Great question-thanks for asking. In Domain-Driven Design (DDD), Customer and Courier are business entities focused on business rules, while User handles authentication. Here’s how they relate: Different Purposes: User stores login and permissions, while Customer and Courier handle business-specific data, like order history or delivery schedules. Link by ID: Instead of mixing login data into Customer or Courier, these entities can include a User ID field that links to the User entity. This way, we keep the roles separate but can still connect a user to their relevant business data. Example: When a customer logs in, the system uses the User ID to load their Customer info, keeping authentication and business data separate. In short, we link User to business entities like Customer by ID without mixing in login details, keeping everything clean and organized! Hope this helps clarify! 😊 Let me know if you have more questions on this topic. 😊

@deadcxlm Ай бұрын

@@learnsmartcoding Thank you very much for your response! If possible, it would be great if you could make a video about DDD and Clean Architecture, and how to separate auth and business entities.

@learnsmartcoding Ай бұрын

Sure, will add to my list

@viznu5481 26 күн бұрын

When does the the component get destroyed for module based and standalone based when lazy loaded ?

@learnsmartcoding 25 күн бұрын

Hi Viznu, Great question! When a lazy-loaded component is destroyed, whether it’s module-based or standalone, the behavior is the same because Angular's lifecycle management is consistent across both approaches. When a Component Gets Destroyed: Module-Based Lazy Loading: The component is destroyed when its view is removed from the DOM, such as when you navigate away from its route or the parent component that hosts the lazy-loaded module is destroyed. Standalone Component Lazy Loading: Similarly, the standalone lazy-loaded component gets destroyed when it is no longer part of the active DOM, typically due to route changes or the destruction of its hosting component. Key Lifecycle Hook: In both cases, the ngOnDestroy lifecycle hook is triggered just before the component instance is destroyed, allowing you to clean up subscriptions, resources, or memory leaks. The main difference between module-based and standalone approaches lies in the structure and modularity, but the lazy loading lifecycle remains identical. Let me know if you'd like further clarification or examples!