Book Image

Building Serverless Web Applications

By : Diego Zanon
Book Image

Building Serverless Web Applications

By: Diego Zanon

Overview of this book

This book will equip you with the knowledge needed to build your own serverless apps by showing you how to set up different services while making your application scalable, highly available, and efficient. We begin by giving you an idea of what it means to go serverless, exploring the pros and cons of the serverless model and its use cases. Next, you will be introduced to the AWS services that will be used throughout the book, how to estimate costs, and how to set up and use the Serverless Framework. From here, you will start to build an entire serverless project of an online store, beginning with a React SPA frontend hosted on AWS followed by a serverless backend with API Gateway and Lambda functions. You will also learn to access data from a SimpleDB database, secure the application with authentication and authorization, and implement serverless notifications for browsers using AWS IoT. This book will describe how to monitor the performance, efficiency, and errors of your apps and conclude by teaching you how to test and deploy your applications.
Table of Contents (17 chapters)
Title Page
Credits
About the Author
About the Reviewer
www.PacktPub.com
Customer Feedback
Preface

Single-Page Applications


In a traditional multipage website, each URL loads a different HTML page. If you are at the example.com page and need to navigate to example.com/about, the entire view will blink with a page reload because it will need to be rendered again. The problem is that, usually, a page reload is a waste of time since both pages share similar content, such as the page header and footer. Also, CSS and JavaScript dependencies may be exactly the same.

In a Single-Page Application, there is a base HTML file that will be loaded for every URL and, depending on the given URL, the inner content will be dynamically loaded to match the address. Also, the URL browsing is controlled at the client-side using JavaScript. Changing from one URL to another will not cause a full page reload. Instead of loading an entire new file, a request is made to the server to retrieve only what is necessary for the new address and just a part of the page will be rendered again.

Pros and cons of SPA

SPA is...