Search icon
Subscription
0
Cart icon
Close icon
You have no products in your basket yet
Arrow left icon
All Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Newsletters
Free Learning
Arrow right icon
Angular Design Patterns and Best Practices

You're reading from  Angular Design Patterns and Best Practices

Product type Book
Published in Feb 2024
Publisher Packt
ISBN-13 9781837631971
Pages 270 pages
Edition 1st Edition
Languages
Author (1):
Alvaro Camillo Neto Alvaro Camillo Neto
Profile icon Alvaro Camillo Neto

Table of Contents (19) Chapters

Preface 1. Part 1: Reinforcing the Foundations
2. Chapter 1: Starting Projects the Right Way 3. Chapter 2: Organizing Your Application 4. Chapter 3: TypeScript Patterns for Angular 5. Chapter 4: Components and Pages 6. Chapter 5: Angular Services and the Singleton Pattern 7. Part 2: Leveraging Angular’s Capabilities
8. Chapter 6: Handling User Inputs: Forms 9. Chapter 7: Routes and Routers 10. Chapter 8: Improving Backend Integrations: the Interceptor Pattern 11. Chapter 9: Exploring Reactivity with RxJS 12. Part 3: Architecture and Deployment
13. Chapter 10: Design for Tests: Best Practices 14. Chapter 11: Micro Frontend with Angular Elements 15. Chapter 12: Packaging Everything – Best Practices for Deployment 16. Chapter 13: The Angular Renaissance 17. Index 18. Other Books You May Enjoy

Communication between components using services

A characteristic that we must understand about Angular services is that, by default, every service instantiated by the dependency injection mechanism has the same reference; that is, a new object is not created, but reused.

This is because the dependency injection mechanism implements the singleton design pattern to create and deliver the objects. The singleton pattern is a design pattern of the creational type and allows the creation of objects whose access will be global in the system.

This characteristic is important for the service because, as the service deal with reusable business rules, we can use the same instance between components, without having to rebuild the entire object. In addition, we can take advantage of this characteristic and use services as an alternative for communication between components.

Let’s change our gym diary so that the ListEntriesComponent component receives the initial list by service...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at €14.99/month. Cancel anytime}