Book Image

Hands-On Full Stack Web Development with Aurelia

By : Diego Argüelles Rojas, Erikson Murrugarra
Book Image

Hands-On Full Stack Web Development with Aurelia

By: Diego Argüelles Rojas, Erikson Murrugarra

Overview of this book

Hands-On Full Stack Web Development with Aurelia begins with a review of basic JavaScript concepts and the structure of an Aurelia application generated with the Aurelia-CLI tool. You will learn how to create interesting and intuitive application using the Aurelia-Materialize plugin, which implements the material design approach. Once you fully configure a FIFA World Cup 2018 app, you'll start creating the initial components through TDD practices and then develop backend services to process and store all the user data. This book lets you explore the NoSQL model and implement it using one of the most popular NoSQL databases, MongoDB, with some exciting libraries to make the experience effortless. You'll also be able to add some advanced behavior to your components, from managing the lifecycle properly to using dynamic binding, field validations, and the custom service layer. You will integrate your application with Google OAuth Service and learn best practices to secure your applications. Furthermore, you'll write UI Testing scripts to create high-quality Aurelia Apps and explore the most used tools to run end-to-end tests. In the concluding chapters, you'll be able to deploy your application to the Cloud and Docker containers. By the end of this book, you will have learned how to create rich applications using best practices and modern approaches.
Table of Contents (19 chapters)
Title Page
Copyright and Credits
Dedication
Packt Upsell
Foreword
Contributors
Preface
Index

Subscribing and publishing events – Event Aggregator at the rescue!


In our current application, we have different components and views. Some of them need to retrieve data from the server, others just need to process data provided for other components, and yet others just help our user interface be more elegant and understandable. Okay, all looks good at this point. Note that at this point, our application supports different kinds of processing—data load, transformation, and how this is displayed. Each one implies a different cost of performance, and because of that one could take longer than others. That being said, let's describe a common scenario—the user enters our application and navigates to the page listing all the matches for this month. There is a lot of data to be retrieved, and you need to calculate the time between today and the match date (for each one).

The time remaining for the cost of all of this operation will depend on the amount of data returned by the server, so you need...