Skip to content

Latest commit

 

History

History
137 lines (91 loc) · 3.84 KB

README.md

File metadata and controls

137 lines (91 loc) · 3.84 KB

kafka-consumer 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/ .

It works in pair with Kafka producer, since the producer relies on the services started by the consumer you have to start the this project before.

Goal of this project

Read messages from Kafka and ensure the consistency:

  • no missing messages
  • no duplicate messages

It operates in two modes:

  • in memory: keep track of the missing messages in a TreeMap
  • persistence: store messages in a PostgreSQL DB

DB operations

Check missing messages (gaps)

select key + 1 as gap_start, 
       next_nr - 1 as gap_end
from (
  select key, 
         lead(key) over (order by key) as next_nr
  from event
) nr
where key + 1 <> next_nr;

Check duplicated messages

select * from (
select key, count(id) as c From event group by key) count_key
where c > 1

Running the application in dev mode

Supporting services

Kafka consumer application requires the following supporting services:

  • Kafka broker
  • PostgreSQL (it's only required if you choose to enable the event persistence)

Quarkus can start those services leveraging the Dev Services. However, in order to test the application failure without dropping the the backend services, it's better to start these services outside of Quarkus.

  1. Dev services must be disabled in application.properties:

    quarkus.devservices.enabled=false
    
  2. Start the backend services via podman kube play from the project root (containing this quarkus project).

    podman kube play kafka-consumer/src/main/kubernetes/dev-services.yaml

Alternatively you can start containers with multiple commands:

  1. Start the kafka container:

    podman run --rm -it -p 9092:9092 -e kafka.bootstrap.servers=OUTSIDE://localhost:9092 docker.io/vectorized/redpanda
  2. Start postgres:

    podman run --rm -it -p 5432:5432 -e POSTGRES_USER=quarkus -e POSTGRES_PASSWORD=quarkus -e POSTGRES_DB=quarkus -v ./kafka-producer/src/main/resources/import.sql:/docker-entrypoint-initdb.d/import.sql:Z docker.io/library/postgres:14

Run it

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/kafka-consumer-1.0.0-SNAPSHOT-runner

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

Deploy in OpenShift

./mvnw install -Dquarkus.kubernetes.deploy=true

Provided Code

RESTEasy JAX-RS

Easily start your RESTful Web Services

Related guide section...