Repository navigation
FAQ
QQQ 4.0 release. Final
4.0.0is available. See QQQ 4.0 for release scope and migration guidance.
Review the LICENSE, NOTICE, and individual source-file headers in the exact framework release and each dependency you select. The repository-level license does not replace component-specific materials. See https://www.qrun.io/licensing for the source links.
Start with the source-based sample, then build one table and one backend process. Learning time depends on your Java experience and application requirements; the documentation does not promise a fixed setup time.
QQQ 4.0 targets Java 21. Application metadata and custom backend steps are Java classes; Maven manages framework dependencies.
The 4.0 modules include relational, MongoDB, SQLite, file-system, S3, and REST backends. Operations and query support vary by backend. A shared action interface does not guarantee cross-backend joins or transactions.
Yes. Build a Java application and run it on infrastructure you control. You configure the database, authentication, TLS, backups, monitoring, and deployment process.
The metadata-driven dashboard supports table layouts, apps, processes, and widgets. Custom frontend work is possible through the application middleware/API contract. This release train uses Material Dashboard 0.41.0.
Configure authentication, permissions, validation, and operational controls explicitly. Test allowed and denied access across every entry point. Framework facilities do not guarantee that an application cannot bypass its intended controls.
Tenant isolation is an application design responsibility. Select an isolation model, apply tenant constraints consistently, and test cross-tenant access through queries, processes, exports, and integrations.
Automatic GraphQL generation is not part of the verified QQQ 4.0 release scope. Any GraphQL adapter requires a separately implemented and tested integration.
QQQ provides processes with Java backend steps and scheduling facilities. Queue delivery, retry policy, idempotency, and recovery depend on the selected implementation and application design.
Consult repository tags and release notes for actual releases. QQQ 4.0.0 is available. See the tagged release notes and migration guidance for its scope and limitations.
Yes. Start with the application, data, or extension template, choose your own Maven coordinates, implement the metadata producer, and test it in a host application. See https://www.qrun.io/docs/tutorials/first-qbit.
Use a qBit's verified Maven coordinates and version, then register its metadata producer in the host application. Follow that component's README. A catalog preview is not an installable package.
QQQ — Java metadata and application behavior.
4.0 release status · GitHub · Documentation · License materials