Book Image

Hands-On Server-Side Web Development with Swift

By : Angus Yeung
Book Image

Hands-On Server-Side Web Development with Swift

By: Angus Yeung

Overview of this book

This book is about building professional web applications and web services using Swift 4.0 and leveraging two popular Swift web frameworks: Vapor 3.0 and Kitura 2.5. In the first part of this book, we’ll focus on the creation of basic web applications from Vapor and Kitura boilerplate projects. As the web apps start out simple, more useful techniques, such as unit test development, debugging, logging, and the build and release process, will be introduced to readers. In the second part, we’ll learn different aspects of web application development with server-side Swift, including setting up routes and controllers to process custom client requests, working with template engines such as Leaf and Stencil to create dynamic web content, beautifying the content with Bootstrap, managing user access with authentication framework, and leveraging the Object Relational Mapping (ORM) abstraction layer (Vapor’s Fluent and Kitura’s Kuery) to perform database operations. Finally, in the third part, we’ll develop web services in Swift and build our API Gateway, microservices and database backend in a three-tier architecture design. Readers will learn how to design RESTful APIs, work with asynchronous processes, and leverage container technology such as Docker in deploying microservices to cloud hosting services such as Vapor Cloud and IBM Cloud.
Table of Contents (18 chapters)

Designing the RESTful API

You can perform the following three easy-to-follow steps to design a RESTful API using HTTP protocols:

  1. Identify an object model to represent one kind of resource.
  2. Define resource endpoints for different levels of resources.
  3. Assign HTTP methods to operations for the resources.

Identifying object models

The resources that are offered to the client are represented as objects on a server. You've already modeled for the content, that is, JournalEntry, and the administrators who have the permission to create, edit, and delete journal entries, that is, Admin. You can identify other objects to represent the resources in your application, such as preferences, user profiles, blogs, and pictures.

The...