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)

Understanding Message and Event Systems

By now, you might be wondering how we are actually connecting microservices together well. The most intuitive and simple answer is that we're providing a (REST) API. There are, however, ways for systems to communicate that are not public but solely internal. They can be classified into one of two groups:

  • Message Systems
  • Event Systems

We will explore both topics in this section.

Let's dive in and start with Message Systems!

Message Systems

Message Systems are part of your infrastructure and allow messages to be sent across the system. This means a microservice can send a message to another service through this system. The question is, how is that different from just using...