DevOps, Continuous Integration & Automated Testing: Rule Them All

Transcription

1 DevOps, Continuous Integration & Automated Testing: Rule Them All SAMIR BEHARA Solution Architect EBSCO, Birmingham, AL

2 DATABASE RELEASE? THE SCRIPTS & I WILL EXECUTE IT

3 Database Lifecycle Management Overview SHIFT LEFT Catch issues as early as possible

4 Automated CI/CD Pipelines

5 Azure DevOps An end-to-end solution for organizations looking for an enterprise-grade toolchain

6 Azure Pipelines and GitHub Integration Cloud-hosted pipelines for Linux, Windows and macos, with unlimited minutes for open source Any language, any platform, any cloud Content Extensible goes here. Content goes here. Content Containers goes here. and Content Kubernetes goes here. Best-in-class for open source

7 Microservices CI/CD Ecosystem

8 Test Driven Development

9 Testing your Microservices Applications

10 Static Code Analysis - SonarQube Continuous Inspection of Code Quality Identify Code Smells, Bugs and Vulnerabilities Analyzers for 20+ Programming Languages DevOps Integration Reject Check-in when Quality Gate not met

11 Release Pipeline

12 Continuous Integration

13 Continuous Delivery Continuous Deployment

14 Feature Flags Potential alternative to maintaining multiple feature branches. Reduces the need for constant branching and merging. Enables releases with unfinished features at no risk.

15 FEATURE FLAGS DEPLOYMENT SCENARIO 1 Scenario: Incremental feature deployment Feature A Feature B DEV QA MOCK PROD Feature A Feature B.1 Feature B.2

16 FEATURE FLAGS DEPLOYMENT SCENARIO 2 Scenario: One passes QA and one fails QA Even though feature A did not receive QA approval, we can still deliver feature B to the customer. We simply switch off the offending feature and create a new task to fix the bug. Feature A Feature A Bug Fix Feature B DEV QA MOCK PROD Feature A Bug Created Feature B Feature A Bug Fix

17 FEATURE FLAGS DEPLOYMENT SCENARIO 3 Scenario: Comparative Performance Enhancement Testing Feature A DEV Feature A < Compare > Gather Performance Data: New Original Feature QA MOCK PROD

18 Scenario: Selectively flipping a feature on need basis in Production Processing Override FEATURE FLAGS DEPLOYMENT SCENARIO 4 We keep this feature flag in production to act as a toggle switch. During busy season we turn it for alternative processing. After busy season, we turn it off and resume normal order processing. DEV QA MOCK PROD Processing Override

19 Blue-Green Deployment

20 Canary Release

21 Dark Release

22 Source Control is the system of truth

23 Database is the system of truth

24 STATE BASED APPROACH State Based Approach Migration Based Approach System of Truth is the Source Code Suited for frequent database changes Suited for large sized teams Source Code contains the current state of the database Less control on the migration script Complex refactoring might take multiple steps System of Truth is the Database Suited for infrequent database changes Suited for small sized teams Have to maintain a long list of migration scripts within the source control More fine grain control on the migration script Complex refactoring can be handled by a single script

25 Any change to the database schema or reference data that was made directly in the database environment, outside of the normal automated delivery pipeline. Ensure that all migrations are idempotent meaning that running a script more than once has no additional impact.

26 Non-Breaking Database Change Adding a Column/Table/Stored Procedure/ View/ Function Breaking Database Change Renaming a Column/Table/Stored Procedure/ View/ Function Dropping a Column/Table Remove a Stored Procedure/ View/ Function Moving a Column from one table

27 Expand and Contract Pattern

28 VERSION CONTROL DISCONNECTED DATABASE DEVELOPMENT DECLARATIVE APPROACH DACPAC DEPLOPYMENTS CODE EDITING EXPERIENCE SCHEMA & DATA COMPARE

29 INCREMENTAL CHANGE SHIFT LEFT MORE CONTROL ON MIGRATION SCRIPT HYBRID Content goes here. Content goes APPROACH here. PROGRAMMABLE OBJECTS OFFLINE SCHEMA MODEL

30 Flyway is free and open source. Flyway facilitates the Automatic Deployment of database changes. Flyway creates a table name schema_version in your database. Flyway supports number of databases Oracle, SQL Server, MySQL, PostgreSQL, MariaDB, SQLite, Redshift and more.

31 Additional Resources Continuous Integration with SQL Server Data Tools in Visual Studio 2017 Database Static Code Analysis using SQL Cop Managing your Technical Debt using SonarQube Continuous Integration, Continuous Delivery and Continuous Deployment

32 Thank You Content here. Content goes here. dotnetvibes.com