chore: Migrated orders component to Spring Data JDBC and PostgreSQL #429
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #17
The open source licensing of both JPA/Hibernate and Java MySQL drivers adds maintenance overhead. This PR migrates the ORM framework from JPA/Hibernate to Spring Data JDBC.
This has also driven a move to Flyway for managing the related database schema. Flyway will automatically perform migrations when the application starts.
Finally, the primary database dependency has moved from MySQL/MariaDB to PostgreSQL. All docker-compose files have been updated to use the correct images, and the Terraform has been modified to use the appropriate AWS infrastructure.
For now the datasource configuration has been simplified to a single datasource. This means the configuration mechanism has changed from:
To this:
The
mysql
Spring profile is also no longer used.