Intermediate

Common Liquibase Design Patterns (LB204)


Description
For users who wish to learn about different Liquibase design patterns. Includes addressing database drift, implementing database guardrails, and utilizing property substitution.

Content
  • Welcome
  • Welcome to the Common Liquibase Design Patterns Course
  • Welcome to the Common Liquibase Design Patterns Course
  • Liquibase Help Resources
  • DESIGN PATTERN 1 - STRUCTURING A NEW LIQUIBASE PROJECT
  • Design Pattern 1 - Structuring a New Liquibase Project Use Case
  • Design Pattern 1 - Common Pipeline Patterns
  • Design Pattern 1 - Parallel Development in an Active Pipeline
  • Design Pattern 1 - One Database with Multiple Applications
  • DESIGN PATTERN 2 - STATE, MIGRATION, AND HYBRID APPROACHES FOR DATABASE CHANGES
  • Design Pattern 2 - State, Migration, and Hybrid-Based Approaches
  • Design Pattern 2 - Using a State-Based Approach
  • Design Pattern 2 - Using a Migration-Based Approach
  • Design Pattern 2 - Using a Hybrid-Based Approach
  • DESIGN PATTERN 3 - DATABASE DRIFT DETECTION
  • Design Pattern 3 - Database Drift
  • Design Pattern 3 - Database Drift Use Case
  • Design Pattern 3 - Exception Handling
  • Design Pattern 3 - Detecting Unintentional Drift
  • Design Pattern 3 - Re-synchronizing Pipeline Environments when Drift Happens
  • Design Pattern 3 - Rebuilding an Environment
  • DESIGN PATTERN 4 - IMPLEMENTING DATABASE GUARDRAILS
  • Design Pattern 4 - Implementing Database Guardrails Use Case
  • Design Pattern 4 - Procedural Guardrails
  • Design Pattern 4 - Ensuring Database Changes are Deployed in Lower Environments
  • Design Pattern 4 - Locking Down Your Git
  • Design Pattern 4 - Enforcing Standards for Database Automation
  • DESIGN PATTERN 5 - UTILIZING PROPERTY SUBSTITUTION IN A LIQUIBASE PROJECT
  • Design Pattern 5 - Property Substitution in a Liquibase Project Use Case
  • Design Pattern 5 - Fundamentals of Property Substitution
  • Design Pattern 5 - Deploying Changesets with Different Tablespace Names
  • Design Pattern 5 - Deploying DML Changes with Environment Specific Values
Completion rules
  • All units must be completed
  • Leads to a certificate with a duration: Forever