Skip to content

KC solution for managing shipping order with command and saga orchestration and IBM MQ

Notifications You must be signed in to change notification settings

ibm-cloud-architecture/eda-kc-order-cmd-mq

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

38 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

KC Solution Order management command microservice with MQ

This microservice implement the Orchestration of the Saga pattern using MQ to support th async request/response communication between Saga participant.

The application uses Quarkus 2.4.x, AMQP and Reactive messaging.

Implementation approach

We are using JAXRS resources and DTO to define OpenAPI contract ().

The resource class transforms DTO to an entity and emits event to Kafka to use it as an append log and transaction.

Continuous Integration

This repo includes a git Action (see .github/workflows folder) to compile and build the image and push to an image registry. To make it working in your own forked repository you need to define the following git Secrets:

Settings > Secrets > New repository secret

  • DOCKER_REGISTRY quay.io or your registry
  • DOCKER_IMAGE_NAME eda-kc-order-ms-mq
  • DOCKER_REPOSITORY ibmcase or your repo
  • DOCKER_USERNAME your-image-registry-username
  • DOCKER_PASSWORD your-image-registry-password

Read more to understand the implementation

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/code-with-quarkus-1.0.0-SNAPSHOT-runner

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

Provided Code

RESTEasy JAX-RS

Easily start your RESTful Web Services

Related guide section...

About

KC solution for managing shipping order with command and saga orchestration and IBM MQ

Resources

Stars

Watchers

Forks

Packages

No packages published