chore: added microprofile-liberty-redis-sentinel sample

Signed-off-by: Maximillian Arruda <[email protected]>

Author: dearrudam

README.adoc

@@ -31,6 +31,11 @@ Open Liberty is a lightweight and highly flexible open-source application server
 | Simple CRUD REST application
 | Redis - Single node
 
+| link:microprofile-liberty-redis-sentinel/[]
+| Simple CRUD REST application
+| Redis - Sentinel
+
+
 |===
 
 == Wildfly

microprofile-liberty-redis-sentinel/.dockerignore

@@ -0,0 +1,3 @@
+target/
+!target/*.war
+!target/liberty/wlp/usr/shared/resources/*

microprofile-liberty-redis-sentinel/.gitignore

@@ -0,0 +1,11 @@
+target/
+pom.xml.tag
+pom.xml.releaseBackup
+pom.xml.versionsBackup
+pom.xml.next
+release.properties
+dependency-reduced-pom.xml
+buildNumber.properties
+.mvn/timing.properties
+# https://github.com/takari/maven-wrapper#usage-without-binary-jar
+.mvn/wrapper/maven-wrapper.jar

microprofile-liberty-redis-sentinel/.mvn/wrapper/maven-wrapper.properties

@@ -0,0 +1,2 @@
+distributionUrl=https://repo.maven.apache.org/maven2/org/apache/maven/apache-maven/3.9.1/apache-maven-3.9.1-bin.zip
+wrapperUrl=https://repo.maven.apache.org/maven2/org/apache/maven/wrapper/maven-wrapper/3.1.1/maven-wrapper-3.1.1.jar

microprofile-liberty-redis-sentinel/Dockerfile

@@ -0,0 +1,10 @@
+
+FROM icr.io/appcafe/open-liberty:kernel-slim-java21-openj9-ubi-minimal
+
+COPY --chown=1001:0 /src/main/liberty/config /config
+
+RUN features.sh
+
+COPY --chown=1001:0 target/*.war /config/apps
+
+RUN configure.sh

microprofile-liberty-redis-sentinel/README.adoc

@@ -0,0 +1,104 @@
+= MicroProfile Open Liberty with Redis sample
+
+This project is intent to be a sample for MicroProfile with MongoDB integration by using Jakarta NoSQL implementation.
+
+== Setup Redis
+
+image::https://jnosql.github.io/img/logos/redis.png[Redis Project,align="center" width=25%,height=25%]
+
+https://redis.com/[Redis] is a software project that implements data structure servers.
+It is open-source, networked, in-memory, and stores keys with optional durability.
+
+The project is configured to reach out a Redis instance with the following configuration:
+
+[source, text]
+----
+host:       localhost
+port:       6379
+----
+
+This Eclipse JNoSQL configuration is defined on the file `src/main/resources/META-INF/microprofile-config.properties`. More info about it, check the following link: https://github.com/eclipse/jnosql-databases?tab=readme-ov-file#configuration-14
+
+[source,properties]
+----
+include::src/main/resources/META-INF/microprofile-config.properties[]
+----
+*PS:warning:* Pay attention to that when you try to set up your own Redis instance.
+
+== Using Docker Compose
+
+The easier way to execute this project is to use the provided docker-compose.yaml file in the root directory.
+You can run it by performing the following command:
+
+[source, bash]
+----
+docker-compose up -d
+----
+
+== Local installation
+
+Follow the instructions in: https://redis.io/docs/latest/operate/oss_and_stack/install/install-redis/
+
+== Using Docker
+
+1. Install docker: https://www.docker.com/
+2. https://hub.docker.com/_/redis
+3. Run docker command
+
+[source, bash]
+----
+docker run -d --name redis-instance -p 6379:6379 redis
+----
+
+== Run the code
+
+The generation of the executable jar file can be performed by issuing the following command
+[source, bash]
+----
+mvn clean package
+----
+
+This will create an executable jar file **microprofile-liberty-redis.jar** within the _target_ maven folder. This can be started by executing the following command
+
+[source, bash]
+----
+java -jar target/microprofile-liberty-redis.jar
+----
+
+=== Liberty Dev Mode
+
+During development, you can use Liberty's development mode (dev mode) to code while observing and testing your changes on the fly.
+With the dev mode, you can code along and watch the change reflected in the running server right away; 
+unit and integration tests are run on pressing Enter in the command terminal; you can attach a debugger to the running server at any time to step through your code.
+
+[source, bash]
+----
+mvn liberty:dev
+----
+
+
+
+
+To launch the test page, open your browser at the following URL
+
+[source, text]
+----
+http://localhost:9080/index.html
+----
+
+
+=== Specification examples
+
+By default, there is always the creation of a JAX-RS application class to define the path on which the JAX-RS endpoints are available.
+
+Also, a simple Hello world endpoint is created, have a look at the class **HelloController**.
+
+More information on MicroProfile can be found [here](https://microprofile.io/)
+
+
+=== Config
+
+Configuration of your application parameters. Specification [here](https://microprofile.io/project/eclipse/microprofile-config)
+
+The example class **ConfigTestController** shows you how to inject a configuration parameter and how you can retrieve it programmatically.
+

microprofile-liberty-redis-sentinel/README.txt

@@ -0,0 +1,35 @@
+After you generate a starter project, these instructions will help you with what to do next.
+
+The Open Liberty starter gives you a simple, quick way to get the necessary files to start building
+an application on Open Liberty. There is no need to search how to find out what to add to your 
+Maven build files. A simple RestApplication.java file is generated for you to start 
+creating a REST based application. A server.xml configuration file is provided with the necessary 
+features for the MicroProfile and Jakarta EE versions that you previously selected.
+
+If you plan on developing and/or deploying your app in a containerized environment, the included 
+Dockerfile will make it easier to create your application image on top of the Open Liberty Docker 
+image.
+
+1) Once you download the starter project, unpackage the .zip file on your machine.
+2) Open a command line session, navigate to the installation directory, and run `./mvnw liberty:dev` (Linux/Mac) or `mvnw liberty:dev` (Windows). 
+   This will install all required dependencies and start the default server. When complete, you will
+   see the necessary features installed and the message "server is ready to run a smarter planet."
+
+For information on developing your application in dev mode using Maven, see the 
+dev mode documentation (https://openliberty.io/docs/latest/development-mode.html).
+
+For further help on getting started actually developing your application, see some of our 
+MicroProfile guides (https://openliberty.io/guides/?search=microprofile&key=tag) and Jakarta EE 
+guides (https://openliberty.io/guides/?search=jakarta%20ee&key=tag).
+
+If you have problems building the starter project, make sure the Java SE version on your 
+machine matches the Java SE version you picked from the Open Liberty starter on the downloads 
+page (https://openliberty.io/downloads/). You can test this with the command `java -version`.
+
+Open Liberty performs at its best when running using Open J9 which can be obtained via IBM Semeru 
+(https://developer.ibm.com/languages/java/semeru-runtimes/downloads/). For a full list of supported 
+Java SE versions and where to obtain them, reference the Java SE support page 
+(https://openliberty.io/docs/latest/java-se.html).
+
+If you find any issues with the starter project or have recommendations to improve it, open an 
+issue in the starter GitHub repo (https://github.com/OpenLiberty/start.openliberty.io).

microprofile-liberty-redis-sentinel/docker-compose.yaml

@@ -0,0 +1,94 @@
+version: '3'
+services:
+  redis-master:
+    container_name: "redis-master"
+    image: redis
+    command: redis-server
+    ports:
+      - "6379:6379"
+    volumes:
+      - redis-master:/data
+
+  redis-slave1:
+    container_name: "redis-slave1"
+    image: redis
+    ports:
+      - "6380:6379"
+    command: redis-server --slaveof redis-master 6379
+    depends_on:
+      - redis-master
+    volumes:
+      - redis-slave1:/data
+
+  redis-slave2:
+    container_name: "redis-slave2"
+    image: redis
+    ports:
+      - "6381:6379"
+    command: redis-server --slaveof redis-master 6379
+    depends_on:
+      - redis-master
+    volumes:
+      - redis-slave2:/data
+
+  redis-sentinel1:
+    container_name: 'redis-sentinel1'
+    image: redis
+    ports:
+      - "26379:26379"
+    command: >
+      sh -c 'echo "bind 0.0.0.0" > /etc/sentinel.conf &&
+      echo "sentinel monitor mymaster redis-master 6379 2" >> /etc/sentinel.conf &&
+      echo "sentinel resolve-hostnames yes" >> /etc/sentinel.conf &&
+      echo "sentinel down-after-milliseconds mymaster 10000" >> /etc/sentinel.conf &&
+      echo "sentinel failover-timeout mymaster 10000" >> /etc/sentinel.conf &&
+      echo "sentinel parallel-syncs mymaster 1" >> /etc/sentinel.conf &&
+      redis-sentinel /etc/sentinel.conf'
+    depends_on:
+      - redis-master
+      - redis-slave1
+      - redis-slave2
+
+  redis-sentinel2:
+    container_name: 'redis-sentinel2'
+    image: redis
+    ports:
+      - "26380:26379"
+    command: >
+      sh -c 'echo "bind 0.0.0.0" > /etc/sentinel.conf &&
+      echo "sentinel monitor mymaster redis-master 6379 2" >> /etc/sentinel.conf &&
+      echo "sentinel resolve-hostnames yes" >> /etc/sentinel.conf &&
+      echo "sentinel down-after-milliseconds mymaster 10000" >> /etc/sentinel.conf &&
+      echo "sentinel failover-timeout mymaster 10000" >> /etc/sentinel.conf &&
+      echo "sentinel parallel-syncs mymaster 1" >> /etc/sentinel.conf &&
+      redis-sentinel /etc/sentinel.conf'
+    depends_on:
+      - redis-master
+      - redis-slave1
+      - redis-slave2
+
+  redis-sentinel3:
+    container_name: 'redis-sentinel3'
+    image: redis
+    ports:
+      - "26381:26379"
+    command: >
+      sh -c 'echo "bind 0.0.0.0" > /etc/sentinel.conf &&
+      echo "sentinel monitor mymaster redis-master 6379 2" >> /etc/sentinel.conf &&
+      echo "sentinel resolve-hostnames yes" >> /etc/sentinel.conf &&
+      echo "sentinel down-after-milliseconds mymaster 10000" >> /etc/sentinel.conf &&
+      echo "sentinel failover-timeout mymaster 10000" >> /etc/sentinel.conf &&
+      echo "sentinel parallel-syncs mymaster 1" >> /etc/sentinel.conf &&
+      redis-sentinel /etc/sentinel.conf'
+    depends_on:
+      - redis-master
+      - redis-slave1
+      - redis-slave2
+
+volumes:
+  redis-master:
+    driver: local
+  redis-slave1:
+    driver: local
+  redis-slave2:
+    driver: local