You will create MySQL databases for the pal-tracker project. MySQL is a good choice for a data store because it is a well-tested relational database. Relational databases are a good fit for almost any data store need.
This lab introduces a tool called Flyway which performs database schema migrations. Migration tools such as Flyway work by tracking changes to the database schema alongside the codebase. This has many benefits:
This lab focuses on migrating a database schema — the table and column structure — from one version to another. It is not about migrating data from one database to another.
The problem of data migration may be related to schema migration. For example, some schema changes may so large that they require data to be transformed and transferred to a new database. However, you would address this using a different set of technologies, such as ETL tools.
After completing the lab, you will be able to:
Review the Services slides.
You must have completed (or fast-forwarded to) the
Spring MVC with REST Endpoints lab.
You must have your
pal-tracker application associated with the
mvc-solution codebase deployed and running on
Tanzu Application Service.
In a terminal window,
make sure you start in the
Pull in the CI migration task.
git cherry-pick migration-start
You may also refer to the Hints section at the end of the lab if you need more assistance.
Create the database service on Tanzu Application Service that you will use later in the lab. You do this here because the MySQL service takes a while to create instances.
cf marketplace command to find a MySQL database service on
your Tanzu Application Service installation.
cf create-service command to create an instance of this
service named tracker-database.
Confirm that the service instance is being created via
cf service tracker-database.
Create a folder in the root of your project called
Create a folder inside the
databases folder called
Create a Database Definition Language (DDL) file called
create_databases.sql with content from the following command:
git show migration-solution:databases/tracker/create_databases.sql
This file will be used to perform the following actions during local development.
trackeruser in the database that has access to the databases.
Create a file called
databases/tracker/migrations/ with content from the following
git show migration-solution:databases/tracker/migrations/V1__initial_schema.sql
This file holds the instructions to create the time entries table with the following columns:
id (integer, primary key)
You will use a date type here because you do not need to track time information. This decision depends on the requirements of the software.
Flyway helps keep track of database versions as a project progresses.
Flyway will automatically run our migrations to the latest version
assuming that the migration file names follow a certain convention.
The convention is
V##__ where the hashes are digits corresponding
to the migration’s order in the list of migrations.
Beware that there two underscores as the delimiter between the version number and the migration description.
Read more about flyway naming conventions here.
Run the DDL file from the earlier step with:
mysql -uroot < databases/tracker/create_databases.sql
This creates the development and test versions of the tracker database, but they do not have any tables or columns yet.
Run the migrations on the development database.
flyway -url="jdbc:mysql://localhost:3306/tracker_dev" -locations=filesystem:databases/tracker clean migrate
User will be
tracker with no password, if you have set up MySQL in
a standard way.
Refer to the Flyway documentation
for alternative installation instructions.
Do the same on the test database.
flyway -url="jdbc:mysql://localhost:3306/tracker_test" -locations=filesystem:databases/tracker clean migrate
Inspect the databases with your favorite MySQL tool and verify that
time_entries table looks correct.
mysql -u tracker
use tracker_dev; describe time_entries;
+------------+--------------+------+-----+---------+----------------+ | Field | Type | Null | Key | Default | Extra | +------------+--------------+------+-----+---------+----------------+ | id | bigint(20) | NO | PRI | NULL | auto_increment | | project_id | bigint(20) | YES | | NULL | | | user_id | bigint(20) | YES | | NULL | | | date | date | YES | | NULL | | | hours | int(11) | YES | | NULL | | +------------+--------------+------+-----+---------+----------------+
You are building a cloud native application which assumes that backing services (like a database) are provided by the platform. Since the pal-tracker application now needs a database, you must create the database service and bind your application to it. This instructs the platform to reserve the instance of the service and then provide the connection information to your application.
cf service or
cf services command to confirm that your
service instance has been created.
Bind the service instance to your application with the
cf bind-service command.
This instructs Tanzu Application Service to provide your
application with the connection information for the MySQL database
you created earlier.
This is given to your application in the
pal-tracker application environment variable is set by
cf env pal-tracker.
Do you see the
VCAP_SERVICES environment variable set in the
Take a look at the updated
The cherry-pick you performed at the beginning of this lab brought
in changes to your
.github/workflows/pipeline.yml file which run a
This script opens an SSH tunnel to your Tanzu Application Service
database and performs migrations.
The database instance that your application has access to is protected by a firewall so you will not be able to connect to it directly. Instead, you can open an SSH tunnel which will use your application as a proxy so that the Flyway CLI running on your CI server can migrate the database managed by Tanzu Application Service.
This functionality does assume you have SSH access on the Tanzu Application Service instance you are working with. This may not be possible in your environment. In this case you should take a look at the Extras section for some ideas as to how you might handle this. You can also look in the Hints for suggestions on how you could use an external database that you have direct access to.
Commit and push your changes.
This will trigger a rebuild and re-deployment to the staging environment that will also perform the migrations on your Tanzu Application Service database.
Review the Migrations slides about database migrations.
Now that you have completed the lab, you should be able to:
Verify whether or not the
VCAP_SERVICES environment variable is
set in the current running
SSH to the running
cf ssh pal-tracker -i 0
VCAP_SERVICES is set:
env |grep VCAP_SERVICES
Do you see the environment variable set in the running container? Why, or why not?
Write a few other migrations if you have additional time.
Explore some of the other Flyway commands and investigate how you can use them to manipulate the database.
Next, implement your migrations using a different versioning scheme.
The migration in this lab runs off-platform — it runs on either a developer workstation, or on the CI/CD server infrastructure. It does not run on the Tanzu Application Service platform.
It is problematic for two reasons:
It requires a tunnel to execute the migration against the managed and brokered MySQL database. Your platform operators will likely not allow and enable tunneling on your Tanzu Application Service platform.
It requires the
pal-tracker application to be pushed before the
migration can be executed,
because the design requires a running container on the platform that
the Flyway migration can tunnel to its network.
That implies you must design into your release workflow to block
traffic to your application until the migration is successfully
You can improve upon this design by the following:
Implement a process/job whose sole function is to run a Flyway migration, that is not the same application that consumes the migrated database. It will run on the Tanzu Application Service platform as a Task, or as a Tanzu Application Service Scheduled Job.
Ensure the migration job is run before the release of the next application version that depends on it. For zero downtime, rolling upgrades, this means your database changes must be backward compatible.
Implement the improved migration:
Create a new Spring boot app named
Use Spring Boot with Flyway Integration to run the Flyway
You can simplify the solution by bundling the Flyway migrations
inside the application resources and reference from the
classpath instead of the file system.
See the following links for help:
Create a Cloud task for your new migration and run it on Tanzu Application Service platform.
This lab assumes that you have some kind of MySQL service available in
your foundation, as shown through the
cf marketplace command.
It is possible that there may be more than one or, perhaps, none at all.
If you have access to the
application, it may be easier to browse
the services marketplace there as the output from
cf marketplace can
be a little hard to read when there are many services.
You will need to find the name of the service and at least one
“service plan” name.
Plans represent a specific configuration of the service,
for example, a particular database size or quality of service.
Here is and edited version of the output from
$ cf marketplace Getting services from marketplace in org neil / space sandbox as neil... OK service plans description broker ... p.mysql db-small, db-medium Dedicated instances of MySQL dedicated-mysql-broker ...
The service name here is
p.mysql and there are two plans available,
Using that information a possible command to create the
cf create-service p.mysql db-small tracker-database
If you can not, or do not want to, create a database service instance within your foundation, you can use a database available outside the foundation.
You can create a
and bind it to your application, in the same way that you bind a service
created from the service catalog.
However, the simplest mechanism may be the same that you will see used
in next lab
for accessing the local database.
That is by setting the
SPRING_DATASOURCE_URL environment variable.
Please be aware, however, that using either method you will need to
migrate-databases.sh script to work with that configuration.