Book Image

Angular 6 for Enterprise-Ready Web Applications

By : Doguhan Uluca
Book Image

Angular 6 for Enterprise-Ready Web Applications

By: Doguhan Uluca

Overview of this book

Angular 6 for Enterprise-Ready Web Applications follows a hands-on and minimalist approach demonstrating how to design and architect high quality apps. The first part of the book is about mastering the Angular platform using foundational technologies. You will use the Kanban method to focus on value delivery, communicate design ideas with mock-up tools and build great looking apps with Angular Material. You will become comfortable using CLI tools, understand reactive programming with RxJS, and deploy to the cloud using Docker. The second part of the book will introduce you to the router-first architecture, a seven-step approach to designing and developing mid-to-large line-of-business applications, along with popular recipes. You will learn how to design a solid authentication and authorization experience; explore unit testing, early integration with backend APIs using Swagger and continuous integration using CircleCI. In the concluding chapters, you will provision a highly available cloud infrastructure on AWS and then use Google Analytics to capture user behavior. By the end of this book, you will be familiar with the scope of web development using Angular, Swagger, and Docker, learning patterns and practices to be successful as an individual developer on the web or as a team in the Enterprise.
Table of Contents (14 chapters)

Angular in Full-Stack Architecture

In this chapter, we will design, architect, create a backlog, and establish the folder structure for your Angular project that will be able communicate with a REST API. This app will be designed to demonstrate the uses of the following:

  • Angular CLI tool (ng)
  • Angular Reuse of UI through components
  • Angular HttpClient
  • Angular Router
  • Angular Reactive Forms
  • Material Autocomplete
  • Material Toolbar
  • Material Sidenav

Regardless of your backend technology, I recommend that your frontend always resides in its own repository and is served using its own web server that is not depended on your API server.

First things first, you need a vision and a road map to act upon.

Wireframe design

There are some...