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)

Using Kubernetes

Kubernetes is a tool that was developed by Google and is now maintained by the Cloud Native Computing Foundation. It is used to manage Docker containers. When we were deploying to Google, it was actually using Kubernetes in the backend. Kubernetes is open source and freely available.

Kubernetes operates with the following main object types:

  • Pod: One or more containers that are running on the same host. It is the basic unit that is used to deploy Docker containers.
  • Service: A group of pods that work together. Each of your microservices would be a service within Kubernetes.
  • Volume: Persistent storage that remains existent, even when a pod is restarted. The normal filesystem loses all its data after a restart in a pod.
  • ConfigMaps and Secrets: These allow us to provide configuration and credentials to containers.

The main idea is that it helps us manage microservices...