Book Image

Hands-On Swift 5 Microservices Development

Book Image

Hands-On Swift 5 Microservices Development

Overview of this book

The capabilities of the Swift programming language are extended to server-side development using popular frameworks such as Vapor. This enables Swift programmers to implement the microservices approach to design scalable and easy-to-maintain architecture for iOS, macOS, iPadOS, and watchOS applications. This book is a complete guide to building microservices for iOS applications. You’ll start by examining Swift and Vapor as backend technologies and compare them to their alternatives. The book then covers the concept of microservices to help you get started with developing your first microservice. Throughout this book, you’ll work on a case study of writing an e-commerce backend as a microservice application. You’ll understand each microservice as it is broken down into details and written out as code throughout the book. You’ll also become familiar with various aspects of server-side development such as scalability, database options, and information flow for microservices that are unwrapped in the process. As you advance, you’ll get to grips with microservices testing and see how it is different from testing a monolith application. Along the way, you’ll explore tools such as Docker, Postman, and Amazon Web Services. By the end of the book, you’ll be able to build a ready-to-deploy application that can be used as a base for future applications.
Table of Contents (19 chapters)

Exploring models

As we have discussed in Chapter 2, Understanding Server-Side Swift, we are dealing with two types of models: database and input/output (I/O) models. We will now create both models and learn how to connect them to Fluent. This section will cover:

  • Database models
  • Connecting models to Fluent
  • I/O models

Let's start with the database models.

Database models

Let's design and create our database models. We need them for Vapor to connect to the database and then return the information within those models.

As we are dealing with users and addresses, we need the following two database models, which we will cover in the next two sections:

  • User
  • Address

Let's start with the user!

...