Java 24

Spring Boot 3

H2 Database (Default values are provided below)

• Default H2 Database Url: http://localhost:8080/h2-console
• username: sa
• password: sa
• url: jdbc:h2:mem:MB_TEST;DB_CLOSE_DELAY=-1

Swagger: http://localhost:8080/swagger-ui/index.html

Flyway for database migration

Centralize exception handling by ControllerAdvice

Mapstruct to map different type of objects to each other

Micrometer dependencies were added to track the logs easily

Testcontainers dependencies were added for integration tests

docker-compose.yml contains Grafana, Prometheus and Zipkin to track metrics, Kafka for event-driven architecture, Redis for caching, Elasticsearch, Kibana, and Logstash for search, analytics engine and logs, PostgreSQL and MongoDB for data storage.

• Kafka and its UI are included for message streaming, while the Elastic Stack (Elasticsearch, Logstash, Kibana) is set up for log management and visualization.
• All services are connected through bridge networks, ensuring communication between containers.
• Actuator: http://localhost:8080/actuator
• Kafka UI: http://localhost:9999/
• Grafana
  • Login Credentials
    • Url: http://localhost:3000/
    • Email or username: admin
    • Password: admin
  • Add Prometheus Datasource
    • Url: http://host.docker.internal:9090
  • Add Dashboards
    • https://grafana.com/grafana/dashboards/4701-jvm-micrometer/
    • https://grafana.com/grafana/dashboards/5373-micrometer-spring-throughput/
• Prometheus
  • Actuator: http://localhost:8080/actuator/prometheus
  • Prometheus: http://localhost:9090/graph
• Zipkin UI: http://localhost:9411
• Elasticsearch: http://localhost:9200/
• Kibana: http://localhost:5601/app/home#/
  • Connect Spring Boot to Elasticsearch (TESTED FOR SPRING BOOT 3)
  • Run Spring Boot project
  • Open http://localhost:5601/app/home#/ --> Discover --> Create data view -> Name should be Index name --> Save date view to Kibana
    • 
• Database credentials
  • PostgreSQL
    • url: jdbc:postgresql://localhost:5432/localdb
    • username: test
    • password: test
  • MongoDB
    • url: mongodb://localhost:27017/testdb?authSource=admin
    • username: root
    • password: example

Test via Postman (OPTIONAL):

1. Import Postman Collection
2. Right-click the imported Postman Collection and click Run Collection section.
3. On the right panel choose Functional or Performance section, edit Run configuration and click run to test the application.

The following command returns all matched data by 'keyPattern:*' pattern

• redis-cli --scan --pattern 'keyPattern:*'

The following command deletes all matched data by 'keyPattern:*' pattern

• redis-cli KEYS 'keyPattern:*' | xargs redis-cli DEL

The following command finds TYPE in redis with KEY

• TYPE key -> TYPE xxx:hashedIdOrSomethingElse

The following commands search by TYPE

• for "string" TYPE: get key
• for "hash" TYPE: hgetall key
• for "list" TYPE: lrange key 0 -1
• for "set" TYPE: smembers key
• for "zset" TYPE: zrange key 0 -1 withScores

RedisInsight: http://localhost:8001/

• After JSON file is downloaded, copy the content of downloaded file and replace play-integrity-credentials.json content with that copied text
• Replace application-name value in application.yml file with project_id variable that is in play-integrity-credentials.json
• HELPFUL LINK BUT IT SHOULD NOT BE NEEDED