Book Image

Implementing Serverless Microservices Architecture Patterns [Video]

By : Richard Takashi Freeman
Book Image

Implementing Serverless Microservices Architecture Patterns [Video]

By: Richard Takashi Freeman

Overview of this book

Building a microservices platform using virtual machines or containers, involves a lot of initial and ongoing effort and there is a cost associated with having idle services running, maintenance of the boxes and a configuration complexity involved in scaling up and down. In this course, We will show you how Serverless computing can be used to implement the majority of the Microservice architecture patterns and when put in a continuous integration & continuous delivery pipeline; can dramatically increase the delivery speed, productivity and flexibility of the development team in your organization, while reducing the overall running, operational and maintenance costs. We start by introducing the microservice patterns that are typically used with containers, and show you throughout the course how these can efficiently be implemented using serverless computing. This includes the serverless patterns related to non-relational databases, relational databases, event sourcing, command query responsibility segregation (CQRS), messaging, API composition, monitoring, observability, continuous integration and continuous delivery pipelines. By the end of the course, you’ll be able to build, test, deploy, scale and monitor your microservices with ease using Serverless computing in a continuous delivery pipeline. Parts of the source code linked to this course are available at https://github.com/PacktPublishing/Implementing-Microservice-Architecture-using-Serverless-Computing-on-AWS
Table of Contents (7 chapters)
Chapter 6
Serverless Continuous Integration and Continuous Delivery Pipelines
Content Locked
Section 1
Continuous Integration and Continuous Delivery
What are the focus and differences of Continuous Integration, and Continuous Delivery, and Continuous Deployment? - Use continuous Integration to focus on automating build and testing to detect issues early - Use Continuous Delivery to focus on automated release process with a human approval step for the production release - Use Continuous Deployment to focus on a fully automated release process without a human approval step for the production release