Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Week3: Presentation Proposal #2404

Merged
merged 6 commits into from
Sep 7, 2024
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
26 changes: 26 additions & 0 deletions contributions/presentation/week3/streuli-mnem/README.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,26 @@
# Assignment Proposal

## Title

Flyway: Version Control for Databases

## Names and KTH ID

- David Streuli ([email protected])
- Muhammadsodiq Nematjanov ([email protected])

## Deadline

- Week 3

## Category

- Presentation

## Description

In this presentation, we will delve into the critical role of automated database version control within the framework of Continuous Deployment. We'll begin by outlining the necessity for managing database schema changes seamlessly alongside application updates to ensure system integrity and performance. We will examine the popular tool Flyway, a popular tool for database versioning. Flyway has been in continual development since 2010 and remains to be the industry standard for database migration and supports over 50 different database platforms. We will discuss how to integrate Flyway into the CI/CD pipeline, ensuring that every deployment reflects both application and database state changes accurately. This presentation will highlight the importance of database versioning to ensure consistency throughout different environments.

**Relevance**

Database versioning is essential in CD as it ensures that database schema changes are consistently and accurately applied across all environments. This automation minimizes downtime and reduces the risk of errors during deployments and thus supports the continuous releasing in typical CD practices.
Loading