Continuous Deployment in the Cloud

In this presentation, I'm showing what is Continous Integration, Continuous Delivery and Continous Deployment. As a context, I'm using cloud microservice architecture.

Transcript

4. Continuous Deployment in the Cloud
5. Agenda 1. Continuous Integration 2. Continuous Delivery 3. Continuous Deployment
6. Michał Górski Lead Software Engineer Northmill AB After the work: • Football • Fantasy Books • Cats • Tea • Traveling michal.gorski.pl@gmail.com michal-gorski
7. Mail microservice
10. Mail microservice
11. • Where is the current state? • How to build? • Is it really working? • Does it compile at least? • How to deploy? Mail microservice
12. Continuous Integration
13. Continuous Integration • Integrate early and often • Run on every commit • Keep the build green at all time • Always remember about tests!
14. Continuous Integration • Integrate early and often • Run on every commit -> On feature and hotfix branches too!! • Keep the build green at all time • Always remember about tests!
15. Continuous Integration • Write tests as part of your stories • Write tests when fixing bugs • Refactoring is an opportunity to add tests • Use code coverage to find untested code
16. Continuous Integration Test Pyramid by Martin Fowler
17. Questions: • Where is the current state? • How to build? • Is it really working? • Does it compile at least? • How to deploy? Continuous Integration
18. Questions: • Where is the current state? • How to build? • Is it really working? • Does it compile at least? • How to deploy? Continuous Integration
19. Questions: • Where is the current state? • How to build? • Is it really working? • Does it compile at least? • How to deploy? Continuous Integration
20. Questions: • Where is the current state? • How to build? • Is it really working? • Does it compile at least? • How to deploy? Continuous Integration
21. Questions: • Where is the current state? • How to build? • Is it really working? • Does it compile at least? • How to deploy? Continuous Integration
22. Questions: • Where is the current state? • How to build? • Is it really working? • Does it compile at least? • How to deploy? Continuous Integration
24. Continuous Delivery
25. Infrastructure as a code { "Description" : "A text description for the template usage", "Parameters": { // A set of inputs used to customize the template per deployment }, "Resources" : { // The set of AWS resources and relationships between them }, "Outputs" : { // A set of values to be made visible to the stack creator }, "AWSTemplateFormatVersion" : "2010-09-09" }
28. Infrastructure as a code "ConfigBucket" : { "Type" : "AWS::S3::Bucket" }
29. "InsertEmail" : { "Type" : "AWS::Serverless::Function", "Properties" : { "Runtime": "dotnetcore2.1", "MemorySize": 1536, "Timeout": 300, "Description": { "Inserting email to the Queue" } "Handler" : "Northmill.Mail::Northmill.Mail.InsertEmailLambda::InsertEmailAsync", "CodeUri" : "bin/Release/netcoreapp2.1/publish", "Role" : {"Fn::GetAtt" : ["LambdaBaseRole", "Arn"]} "Environment" : { "Variables" : { "MailQueueUrl" : {"Ref" : "MailQueue"}, "ConfigBucket" : {"Ref" : "ConfigBucket"} } } }
30. "LambdaBaseRole" : { "Type" : "AWS::IAM::Role", "Properties" : { "ManagedPolicyArns" : [ "arn:aws:iam::aws:policy/AmazonS3FullAccess", "arn:aws:iam::aws:policy/service-role/AWSLambdaRole", "arn:aws:iam::aws:policy/AWSXrayWriteOnlyAccess" ], "AssumeRolePolicyDocument" : { "Version" : "2012-10-17", "Statement" : [{ "Effect" : "Allow", "Action" : ["sts:AssumeRole"], "Principal" : {"Service" : ["lambda.amazonaws.com"]} }] } }
33. Questions: • Where is the current state? • How to build? • Is it really working? • Does it compile at least? • How to deploy? Continuous Delivery
34. Questions: • Where is the current state? • How to build? • Is it really working? • Does it compile at least? • How to deploy? Continuous Delivery
36. Continuous Delivery • Small changes • Automate everything • Smoke Testing • Contract Testing
37. Contract Tests
38. Continuous Deployment
39. Continuous Deployment • Strong Continuous Integration • Good test coverage • Real-time monitoring • Post-deployment tests • CD culture in other departments(Product, Marketing, Analytics...) • Feature Toggles
41. Continuous Deployment • Small changes • Automate everything • Smoke Testing • Contract Testing • Feature Toggles • Constant flow of new features • No “Release day” problems
42. Thank you!! Q&A