Book Image

Angular Services

Book Image

Angular Services

Overview of this book

A primary concern with modern day applications is that they need to be dynamic, and for that, data access from the server side, data authentication, and security are very important. Angular leverages its services to create such state-of-the-art dynamic applications. This book will help you create and design customized services, integrate them into your applications, import third-party plugins, and make your apps perform better and faster. This book starts with a basic rundown on how you can create your own Angular development environment compatible with v2 and v4. You will then use Bootstrap and Angular UI components to create pages. You will also understand how to use controllers to collect data and populate them into NG UIs. Later, you will then create a rating service to evaluate entries and assign a score to them. Next, you will create "cron jobs" in NG. We will then create a crawler service to find all relevant resources regarding a selected headline and generate reports on it. Finally, you will create a service to manage accuracy and provide feedback about troubled areas in the app created. This book is up to date for the 2.4 release and is compatible with the 4.0 release as well, and it does not have any code based on the beta or release candidates.
Table of Contents (15 chapters)
Angular Services
Credits
About the Author
About the Reviewer
www.PacktPub.com
Customer Feedback
Preface

Introducing the anatomy of cure and prevention


The logic behind cure and prevention is very simple and it is all about timing: whatever issue we find AFTER running the application will be considered as a situation that needs a cure. On the other side, the very next time that we use that solution BEFORE the issue arises then we consider it as prevention. So technically what we call a cure here is a note that mentions something is broken and it needs our attention. It simply informs us about it and does not patch it up by itself.

Tip

Please keep in mind that there are situations where we cannot find problems until after code execution. For example, we cannot find out if the query result is valid and is within the acceptable range, without letting the Google CSE (Custom Search Engine) do its job. So what happens at that point onward - technically- is a cure, not prevention.

That means we cannot save the query quota before trying something. However, we can save the Firebase quota and database space...