Roadmap
Scheduled Reports
Cron-based generation for daily, weekly, monthly, and tenant-specific reports.
- Cron schedules
- Timezone-aware generation
- Retry policy
- Run history
Platform
Start embedded. Standardize reporting across services tomorrow.
Report-Boot is useful today as an embedded Spring Boot reporting framework. It is also designed to evolve into a platform foundation for enterprise and microservice environments. Current capabilities are marked separately from roadmap direction.
Advanced features
Automation, performance, storage, and observability.
These are the advanced capabilities around the core reporting engine. Some exist today through the embedded library and configuration model; others are platform roadmap items.
Roadmap
Scheduled Report Emails
Send generated reports as attachments or secure expiring links.
- Dynamic recipients
- Email templates
- Retry and failure tracking
Available
High Performance Caching
Reduce repeated work by caching templates, metadata, and renderer lookups.
- Template caches
- DTO metadata cache
- Renderer support lookup cache
Available
Startup Report Compilation
Validate provider templates during startup so bad reports fail early.
- Compile on startup
- Fail on startup error
- Java 21 virtual-thread friendly
Roadmap
NoSQL Report Archive Storage
Archive generated report metadata and content for scalable retrieval.
- MongoDB/OpenSearch direction
- Redis download cache direction
- Retention cleanup
Roadmap
Object Storage Integration
Store large reports outside application memory for distributed deployments.
- S3/MinIO direction
- Signed URL direction
- Tenant prefixes
Roadmap
Async Report Generation
Submit long-running reports and poll status or receive callbacks.
- Submit/status/download flow
- Background workers
- Cancellation and retries
Roadmap
Webhook Notifications
Notify external systems when generation completes, fails, expires, or downloads.
- report.generated
- report.failed
- report.expired
- report.downloaded
Roadmap
Observability & Metrics
Operational visibility through metrics, structured logs, and provider diagnostics.
- Render duration
- Provider failures
- Storage latency
- Cache hit rate
Roadmap
Data Source Integrations
Future provider direction for reports enriched from external sources.
- REST provider direction
- CSV/ETL provider direction
- GraphQL direction
Roadmap
Marketplace Package Importer
Import marketplace report packages directly into Spring Boot applications.
- DTO and template import
- Sample request
- Field contract validation
Roadmap
Report Preview & Dry Run
Validate a report package before storing or sending final output.
- Required field checks
- Template existence
- Engine/output compatibility
Enterprise features
Technical coverage for service-owned reporting.
This section is written for backend and platform engineers. It separates what the embedded runtime can do today from the server-mode direction needed for multi-service deployments, shared storage, queue-backed jobs, gateway context, and platform observability.
Today
11 runtime capabilities
Providers
5 rendering paths
Boundary
tenant + lifecycle
Direction
server mode roadmap
Implemented
Embedded Runtime Integration
Use Report-Boot inside an existing Spring Boot service when the service already owns the data, identity, and business rules.
- Direct ReportService call
- No network hop
- Keeps service data local
- Works with existing Spring context
Implemented
Service-Owned Report Contracts
Treat reports as reviewed application contracts, not hidden export scripts scattered across controllers.
- Annotation DTO contracts
- SQL definition contracts
- Versionable templates
- Code-reviewable report behavior
Implemented
Provider-Neutral Pipeline
A shared dispatch path selects the renderer and returns a common generated report model across engines.
- JasperReports
- JXLS
- BIRT
- Thymeleaf
- Dynamic Excel
- GeneratedReport response
Implemented
SQL Dynamic Excel Runtime
Generate operational workbooks directly from named SQL definitions when teams need query-first reports.
- Named parameters
- Multi-sheet workbooks
- Column-name formulas
- Summary footers
- Metadata sheet
Implemented
Report Order Lifecycle
Generated files are handled through a lifecycle object instead of returning anonymous bytes from every feature.
- Report order UUID
- Download validation
- Expiry policy
- Filename/content type
- Generated timestamp
Implemented
Tenant-Aware SQL Boundary
SQL reports can enforce tenant context so exports do not bypass the same isolation expected by application APIs.
- Tenant column mapping
- Tenant parameter name
- Token-based detection
- Missing-tenant failure path
Implemented
Large Workbook Controls
Streaming Excel settings make memory, disk, and sheet overflow behavior explicit for large exports.
- Window size
- Max rows per sheet
- Overflow policy
- Compressed temp files
- Auto-size sampling
Implemented
Java 21 Concurrency Fit
Report generation is designed to fit modern Java services, including independent sheet/query work that can use virtual-thread-friendly execution.
- Independent sheet loading
- Multi-query workbooks
- Service-local execution
- No central queue required today
Implemented
Diagnostics Policy
Production logs should show the actionable root cause by default, with full traces enabled only when troubleshooting needs them.
- Compact root-cause logs
- Trace property
- Provider-level error context
- Cleaner local development
Implemented
Configuration Standardization
Shared YAML properties help teams configure report behavior consistently across services and environments.
- Template paths
- Download expiry
- Watermark policy
- SQL tenant settings
- Excel streaming defaults
Available
Sensitive Report Marking
Watermarking supports controlled distribution when generated files contain internal, user, or tenant data.
- Static watermark values
- User/tenant values
- Timestamp
- Report UUID
Roadmap
Central Reporting Service Direction
For organizations that outgrow embedded-only reporting, Report-Boot can evolve toward a dedicated server mode.
- REST generate API
- Submit/status/download flow
- Shared repository
- Async workers
Roadmap
Gateway Context Propagation
A central service needs explicit trusted context from the edge or gateway instead of guessing tenant and user state.
- Authorization token
- X-Tenant-Id
- X-Correlation-Id
- X-Requested-By
Roadmap
Storage & Repository Strategy
Multi-instance deployments need durable report metadata and file storage outside application memory.
- JDBC report repository
- Filesystem storage
- Object storage
- Retention cleanup
Roadmap
Deployment & Worker Roadmap
Future platform packaging should support local evaluation, production deployment, and queue-backed background generation.
- Docker image
- Compose demo
- Kubernetes manifests
- Helm chart
- RabbitMQ/Kafka workers
Roadmap
Platform Observability Direction
A reporting platform should expose health, readiness, correlation, and renderer/storage metrics like any other service.
- Actuator health
- Readiness/liveness
- Provider health
- Storage latency
- Correlation IDs
Platform and microservice roadmap
Future server-mode capabilities
These items are roadmap/platform direction, not current embedded-library claims. The current recommendation is to start embedded, standardize conventions, and move to central service mode only when the organization has a clear platform need.
Roadmap
Standalone Report-Boot Server
Roadmap
REST generation API
Roadmap
Async report jobs
Roadmap
Shared filesystem storage
Roadmap
JDBC report repository
Roadmap
Docker image and Compose demo
Roadmap
Kubernetes manifests
Roadmap
Helm chart
Roadmap
API Gateway examples
Roadmap
REST client starter
Roadmap
RabbitMQ/Kafka worker modules
Roadmap
Observability and health checks