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)

Environment variables

You learned how to pass configuration variables to your Vapor app on macOS in Chapter 3, Getting Started with the Vapor Framework. By simply making environment variables available, the application knows of your configuration credentials. On macOS, this looks like this:

export DATABASE_USER="user"

The same also works on a server that is not macOS. Note that your server may expect the variables in a different format, depending on the specific Linux distribution. In general, you want to make sure you know how to provide the environment variables to your application at runtime. You do not want to expose them to your code as defaults or in the Docker image.

Your credentials could get exposed through having them in your image, which poses a security threat but also makes it harder for you to change them. Therefore, you want to keep them flexible and out...