Book Image

Expert AWS Development

By : Atul Mistry
Book Image

Expert AWS Development

By: Atul Mistry

Overview of this book

Expert AWS Development begins with the installation of the AWS SDK and you will go on to get hands-on experience of creating an application using the AWS Management Console and the AWS Command Line Interface (CLI). Then, you will integrate applications with AWS services such as DynamoDB, Amazon Kinesis, AWS Lambda, Amazon SQS, and Amazon SWF. Following this, you will get well versed with CI/CD workflow and work with four major phases in the release process – Source, Build, Test, and Production. Then, you will learn to apply AWS Developer tools to your Continuous Integration (CI) and Continuous Deployment (CD) workflow. Later, you will learn about user authentication using Amazon Cognito, and also how you can evaluate the best architecture as per your infrastructure costs. You will learn about Amazon EC2 service and will deploy an app using it. You will also deploy a practical real-world example of a CI/CD application with the Serverless Application Framework, which is known as AWS Lambda. Finally, you will learn how to build, develop, and deploy the Application using AWS Developer tools such as AWS CodeCommit, AWS CodeBuild, AWS CodeDeploy, and AWS CodePipeline, as per your project requirements.
Table of Contents (16 chapters)
Title Page
Packt Upsell

Chapter 3. Continuous Integration and Continuous Deployment Workflow

Development and Operations (DevOps) is the buzzword in current market trends; it is a practice/approach/methodology/process for continuous software development, testing, integration, deployment, and for managing environments.

In this chapter, we will cover Continuous Integration (CI) and Continuous Deployment (CD) workflows, and also see the difference between Continuous Delivery and Continuous Deployment. We will explore various types of tool to use in the DevOps process.

CI is the workflow strategy which ensures that everyone's code changes integrate with the current repository; it endeavors to catch bugs and reduce merge conflicts.

Continuous Delivery is the next step after CI, in which developers are developing software in such a way that they can release it at any time. Sometimes people are confused about Continuous Delivery (CD) and Continuous Deployment (CD), so we will discuss this later in this chapter.