Skip to main content

framework-quarkus-jnosql

Provides Cloud-Native development patterns with Quarkus, GraalVM Native Image, and polyglot NoSQL persistence using Eclipse JNoSQL, Jakarta NoSQL, and Jakarta Data.

Source facts

Repository
dandgabr/Coacus
Last source activity
September 20, 2026 at 03:33
Detected SKILL.md language
English
Stars
4
Forks
3

Install options

The review-first prompt is selected by default. You can switch to a direct command or download a local copy.

Review the source files

Read SKILL.md and any companion files shown by SkillsMP before deciding whether to install.

File Explorer
5 files

Showing SKILL.md

SKILL.md
Source instructions · Read-only preview
name
framework-quarkus-jnosql
description
Provides Cloud-Native development patterns with Quarkus, GraalVM Native Image, and polyglot NoSQL persistence using Eclipse JNoSQL, Jakarta NoSQL, and Jakarta Data.
# Quarkus & Eclipse JNoSQL Cloud-Native Engineering This skill establishes advanced Cloud-Native development standards in Java using the **Quarkus** and **Eclipse JNoSQL** (Jakarta NoSQL / Jakarta Data) ecosystem. --- ## 🧭 1. Quarkus Fundamentals and Philosophy - **Supersonic Subatomic Java**: Instant startup and an ultra-low memory footprint through Ahead-of-Time (AOT) compilation with GraalVM Native Image. - **Build-Time Metaprogramming**: Dependency injection via ArC (static CDI resolved at compile time) and elimination of dynamic reflection. - **Unified Reactive and Imperative Architecture**: Transparent support for blocking calls managed by Virtual Threads or reactive code with Mutiny. --- ## 🗄️ 2. Polyglot Persistence with Eclipse JNoSQL and Jakarta Data - **Supported Models**: - *Document*: MongoDB, Couchbase. - *Key-Value*: Redis, DynamoDB. - *Columnar*: Apache Cassandra, ScyllaDB. - *Graph*: Neo4j. - **Jakarta Data Repository Pattern**: - Declarative interface extending typed repositories: ```java @Repository public interface CustomerRepository extends CrudRepository<Customer, String> { List<Customer> findByCity(String city); } ``` - **Entity Mapping**: `@Entity`, `@Id`, and `@Column` annotations that are independent of the underlying database, guaranteeing portability across NoSQL providers. --- ## 🚀 3. Best Practices for GraalVM Native Image - Avoid dynamic classes, CGLIB proxies, and undeclared reflection. - Register DTOs and JSON serialization entities with `@RegisterForReflection`. - Keep Quarkus Dev Mode (`quarkus dev`) active for instant hot reload during the development cycle.
View on GitHub