Repository navigation
Core Modules
QQQ 4.0 release. Final
4.0.0is available. See QQQ 4.0 for release scope and migration guidance.
The core reactor publishes the following 18 coordinates. Import qqq-bom-pom in dependency management, then add only the modules your application uses. See installation for complete Maven syntax.
Artifact (com.kingsrook.qqq) |
Packaging |
|---|---|
qqq-parent-project |
POM |
qqq-bom-pom |
POM |
qqq-backend-core |
JAR |
qqq-backend-module-api |
JAR |
qqq-backend-module-filesystem |
JAR |
qqq-backend-module-rdbms |
JAR |
qqq-backend-module-sqlite |
JAR |
qqq-backend-module-postgres |
JAR |
qqq-backend-module-mongodb |
JAR |
qqq-language-support-javascript |
JAR |
qqq-openapi |
JAR |
qqq-middleware-picocli |
JAR |
qqq-middleware-javalin |
JAR |
qqq-middleware-lambda |
JAR |
qqq-middleware-slack |
JAR |
qqq-middleware-api |
JAR |
qqq-middleware-health |
JAR |
qqq-utility-lambdas |
JAR |
Backend modules provide storage-specific action implementations. Middleware modules provide configured HTTP, command-line, event, or other application entry points. Core has its own third-party dependencies; it is not dependency-free.
The sample is outside the root reactor. Material Dashboard 0.41.0 is a separate repository and dependency. S3 support belongs to the filesystem facilities; it is not an additional reactor coordinate. Review the actual backend implementation before assuming support for a storage vendor, operation, query feature, or transaction boundary.
QQQ — Java metadata and application behavior.
4.0 release status · GitHub · Documentation · License materials