![Tools of the Trade
I [Nathan Voxland] would summarize the differences as:
!
FlyWay is "lower level" with you specifying exactly the SQL
you want ran whereas Liquibase is "higher level" with you
specifying what you want changed and Liquibase
computing the SQL
!
FlyWay manages changes by filename whereas Liquibase
manages changes by order in a file.
Nathan Voxland, Liquibase developer](https://image.slidesharecdn.com/13af7916-7419-4031-af59-1776df31a814-151209063941-lva1-app6892/85/Javaone-2014-42-320.jpg)
Javaone 2014
- 1. Database migrations the missing piece in Java EE BOF3528 Rikard Thulin
- 2. This is a short version of this talk ! Full length video available at: http://vimeo.com/105880153 Rikard Thulin
- 3. We will discuss how schema migrations improves the software engineering life cycle and the possibilities to improve Java for the future
- 4. Roadmap • Introduction to the topic and why it is so important (7 min) • Schema Migrations demo (8 min) • The current situation, the tools of the trade (5 min) • Future possibilities at hand to solve this problem (5 min) • Discussion (15 min)
- 5. About me
- 6. Part 1 ! Introduction to the topic and why it is so important
- 7. Staging clusterCI How do we keep everything CONSISTENT? QA Staging cluster Prod clusterProd cluster Dev team
- 8. {code} VCS Build server How do we keep { code } CONSISTENT? artifacts Repository push pull publish release QA promote DEV/CIStaging Prod Dev team
- 9. What is the problem?
- 10. Two entities
- 13. Really? Is the database EVIL?
- 14. artifact manual, script, … Source Database
- 15. HOW
- 16. artifact manual, script, … Source Database db deltas, automatic
- 17. artifact Source
- 18. {code + migrations} VCS Build server How do we keep { code + database } CONSISTENT? artifacts {code + migrations} Repository push pull publish release QA promote Staging Prod Dev team DEV/CI
- 19. Shiny Happy People We get
- 20. Schema Migration DEMO DEMO DEMO DEMO
- 21. Schema Migration DEMO DEMO DEMO DEMO Migrations are applied automatically during deployment
- 22. Schema Migration DEMO DEMO DEMO DEMO Spring based application
- 24. LOCAL DEV PROD Version 0 Version 0 Version 0
- 25. LOCAL DEV PROD Version 1 Version 0 Version 0
- 26. LOCAL DEV PROD Version 1 Version 1 Version 0
- 27. LOCAL DEV PROD Version 2 Version 1 Version 0
- 28. LOCAL DEV PROD Version 2 Version 3 Version 0
- 29. LOCAL DEV PROD Version 2 Version 3 Version 3
- 30. What can we do? create/drop TABLE create/drop INDEX add/remove CONSTRAINT java REFACTORINGS STORED PROCEDURES create/drop VIEWS insert DATA ! and more!
- 31. What is the trick?
- 32. When is the trick?
- 33. Another view Automatization of: a sequences of instructions to be executed given the revision of the source code
- 34. Database Change Management Real Life Tricks • Possible to use on an existing database • Quick and simple to implement • Database copies mix and match • Wash copies of production database • DBA approval / review process • One click release possible
- 35. Part 2 ! The current situation tools of the trade
- 37. Tools of the Trade ActiveRecord Ruby (Ruby) Entity Framework Migrations (.net) COMPETITION HAS IT
- 38. Tools of the Trade Hibernate & JPA Schema Generation
- 39. Tools of the Trade FlyWay & Liquibase Stronger execution order Supports different DB / environment Stereotype of being “heavyweight" Automatic rollback Convention over configuration Gaining popularity
- 40. Tools of the Trade FlyWay Convention over configuration Get up and running in 5 minutes Gaining popularity
- 41. Tools of the Trade Liquibase Stronger execution order Supports different DB for different environment Stereotype of being “heavyweight" Automatic rollback
- 42. Tools of the Trade I [Nathan Voxland] would summarize the differences as: ! FlyWay is "lower level" with you specifying exactly the SQL you want ran whereas Liquibase is "higher level" with you specifying what you want changed and Liquibase computing the SQL ! FlyWay manages changes by filename whereas Liquibase manages changes by order in a file. Nathan Voxland, Liquibase developer
- 43. Tools of the Trade summary Schema migration is •Not solved by Java EE today •Solved by 3PP •Already in competitors standards
- 44. Part 3 ! Future possibilities to solve this problem
- 45. The future my proposal Add schema migration to Java EE
- 46. Reasons to add Migrations to Java EE We are behind the competition Schema migrations is not well know to the broad developer community Increased Quality and Productivity Adding complexity to the platform
- 48. the future? class User { }
- 49. @Migration(id="1", author="duke") class CreateUserTable { ! @CreateTable(User.class) @AddColumn(User.class) long id; ! @AddColumn(entity = User.class, size = "255") String name; } the future? Warning: the following slides are possibilities for the future — not what we have
- 50. the future? @Migration(id="1", author="duke") class CreateUserTable { @AddColumn(User.class) long id; … } @Entity class User { @Id long id; … } Migration2Code Generator Warning: the following slides are possibilities for the future — not what we have
- 51. @Entity class User { ! @Id long id; ! @Column(size="255") String name; } the future?
- 52. @Migration(id="2", author="duke") class AddColumnsToUser { ! @DropColumn(User.class) String name; ! @AddColumn(entity = User.class, size="80") String firstName; ! @AddColumn(entity = User.class, size="80") String lastName; ! @AddColumn(entity = User.class, size="255") String email; } the future? Warning: the following slides are possibilities for the future — not what we have
- 53. @Entity class User { ! @Id long id; ! @Column(size="80") String firstName; ! @Column(size="80") String lastName; ! @Column(size="255") String email; } the future?
- 54. Wrap up YOU! Should use Schema Migration WE? JCP JSR! " What? Lets figure it out!" When? Now. Lets start! rikard.thulin@squeed.com
- 55. Discussion and Q & A rikard.thulin@squeed.com