How does Spring Boot manage database schema migrations (Flyway vs Hibernate ddl-auto)? स्प्रिंग बूट डेटाबेस स्कीमा माइग्रेशन को कैसे मैनेज करता है (Flyway बनाम Hibernate ddl-auto)?

spring.jpa.hibernate.ddl-auto lets Hibernate generate or update the schema automatically based on entity classes (values like update, create, validate, none), which is convenient for local development but risky in production since it can silently alter or drop columns and offers no versioned history.

Flyway (or Liquibase) manages schema changes as versioned, reviewable SQL migration scripts (e.g. V1__init.sql, V2__add_email_column.sql) that run in order and are tracked in a schema history table, giving predictable, auditable, and rollback-friendly migrations. The recommended production pattern is ddl-auto=validate (or none) paired with Flyway managing the actual schema changes.

# application.properties
spring.jpa.hibernate.ddl-auto=validate
spring.flyway.enabled=true
spring.flyway.locations=classpath:db/migration