db-syncer Project

This project uses Quarkus, the Supersonic Subatomic Java Framework.

If you want to learn more about Quarkus, please visit its website: https://quarkus.io/ .

Running the application in dev mode

You can run your application in dev mode that enables live coding using:

./mvnw compile quarkus:dev

NOTE: Quarkus now ships with a Dev UI, which is available in dev mode only at http://localhost:8080/q/dev/.

Packaging and running the application

The application can be packaged using:

./mvnw package

It produces the quarkus-run.jar file in the target/quarkus-app/ directory. Be aware that it’s not an über-jar as the dependencies are copied into the target/quarkus-app/lib/ directory.

The application is now runnable using java -jar target/quarkus-app/quarkus-run.jar.

If you want to build an über-jar, execute the following command:

./mvnw package -Dquarkus.package.type=uber-jar

The application, packaged as an über-jar, is now runnable using java -jar target/*-runner.jar.

Creating a native executable

You can create a native executable using:

./mvnw package -Pnative

Or, if you don't have GraalVM installed, you can run the native executable build in a container using:

./mvnw package -Pnative -Dquarkus.native.container-build=true

You can then execute your native executable with: ./target/db-syncer-0.1-SNAPSHOT-runner

If you want to learn more about building native executables, please consult https://quarkus.io/guides/maven-tooling.

Provided Code

RESTEasy Reactive

Easily start your Reactive RESTful Web Services

Related guide section...

Deploying DB on kubernetes

MySQL

1. Deploy DB kubectl kustomize deploy/mysql | kubectl -n <namespace> apply -f -
2. Populate DB kubectl -n <namespace> exec deployment/mysql -- mysql -uroot -proot < src/test/resources/populate.sql
3. Port forward DB endpoint kubectl -n <namespace> port-forward deployment/mysql 3306:3306
4. Run the cache-manager locally docker run -it -p 11222:11222 -p 8080:8080 quay.io/gingersnap/cache-manager
5. Run DB-Syncer locally quarkus dev

Postgres

1. Deploy DB kubectl kustomize deploy/postgres | kubectl -n <namespace> apply -f -
2. Populate DB kubectl -n mysql exec -it deployment/postgres -- psql -U root -d debeziumdb -a < src/test/resources/populate.sql
3. Port forward DB endpoint kubectl -n <namespace> port-forward deployment/postgres 5432:5432
4. Run the cache-manager locally docker run -it -p 11222:11222 -p 8080:8080 quay.io/gingersnap/cache-manager
5. Run DB-Syncer quarkus dev

Deploying DB with Docker Compose

MySQL

Requirements:

1. Make sure docker is running and you have docker-compose available
2. Run docker-compose -f deploy/mysql/mysql-compose.yaml up to start mysql exposed on 3306 and adminer on 8090 Adminer can be looked at via a browser at localhost:8090 as an administration tool. Login is user: root, password: root. You may need to refresh the schema to see the debezium one.
3. Run the cache-manager locally docker run -it -p 11222:11222 -p 8080:8080 quay.io/gingersnap/cache-manager-mysql
4. Run quarkus dev from the poc base directory. This will run with the quarkus endpoint on 8080 and remote JVM debug on 5005. Our client creates the cache it uses debezium-cache
5. Perform inserts and updates to the database Running docker exec -i <container id> mysql -uroot -proot < src/test/resources/populate.sql will execute some operations in the database. To exit, press q in the terminal running the application, so the offset is flushed.

Postgres

Requirements:

1. Make sure docker is running and you have docker-compose available
2. Run docker-compose -f deploy/postgres/postgres-compose.yaml up to start Postgres exposed on 5432
   • This will create the database, user, schema, and tables necessary for testing.
3. Run the cache-manager locally docker run -it -p 11222:11222 -p 8080:8080 quay.io/gingersnap/cache-manager-postgresql
4. Run quarkus dev -Dquarkus.profile=pgsql from the poc base directory.
   • This will run with the quarkus endpoint on 8080 and remote JVM debug on 5005. Our client creates the cache it uses debezium-cache.
5. Perform inserts and updates to the database
   • Running docker exec -i <container id> psql -U root -d debeziumdb -a < src/test/resources/populate.sql will execute some operations in the database.
   • To exit, press q in the terminal running the application, so the offset is flushed.

SQL Server

To run with SQL server some additional setup is required.

1. Make sure docker is running and you have docker-compose available
2. Run docker-compose -f deploy/mssql/mssql-compose.yaml up to start Postgres exposed on 5432
   • This will create the database, user, schema, and tables necessary for testing.
3. Run the cache-manager locally docker run -it -p 11222:11222 -p 8080:8080 quay.io/gingersnap/cache-manager-mssql

Now is necessary to enable the SQL Server Agent and CDC for the tables:

1. Run sh deploy/mssql/after.sh
   • This will start the agent and configure CDC for the customer table

Now with everything setup:

1. Run quarkus dev -Dquarkus.profile=mssql from the poc base directory.
   • This will run with the quarkus endpoint on 8080 and remote JVM debug on 5005.
2. Perform inserts and updates to the database. Use container with MS tools
   • Execute docker exec -it mssql_tools_1 /bin/bash
   • Inside the container execute sqlcmd -S sqlserver -U sa -P 'Password!42' -d debezium
   • Use T-SQL to issue commands

Oracle Database

Requirements:

1. Make sure docker is running and you have docker-compose available
2. Run docker-compose -f deploy/oracle/oracle-compose.yaml up to start Oracle Database exposed on 1521
   • This will create the database, user, schema, and tables necessary for testing.
3. Run the cache-manager locally docker run -it -p 11222:11222 -p 8080:8080 quay.io/gingersnap/cache-manager-oracle
4. Run quarkus dev -Dquarkus.profile=oracle+dev from the poc base directory.
   • This will run with the quarkus endpoint on 8080 and remote JVM debug on 5005.
5. Perform inserts and updates to the database
   • Running cat ./src/test/resources/oracle/populate.sql | docker exec -i <container id> sqlplus -S debezium/dbz@XEPDB1 will execute some operations in the database.
   • To exit, press q in the terminal running the application, so the offset is flushed.