Releases: Nishant040305/vayureader
VayuReader 2.0.0
VayuReader v2.0.0 Release Notes
Overview
VayuReader 2.0.0 marks a significant architectural evolution of the platform, transitioning from a rigid, branch-based implementation to a flexible, configuration-driven system. This release focuses on improving performance, scalability, and deployment adaptability while maintaining strong security capabilities.
The new version enables organizations to tailor the platform based on their specific requirements, balancing security and performance through feature flags and modular components.
Key Highlights
1. Configuration-Driven Architecture
The most important change in v2.0.0 is the shift to a unified, configuration-based system.
Previously:
- Separate branches handled security-heavy and performance-focused implementations.
Now:
- A single codebase supports multiple deployment modes.
- Features can be enabled or disabled via configuration.
Configurable features include:
- End-to-End Encryption (E2E)
- DPoP (Demonstration of Proof of Possession)
- Request-level signing
This approach simplifies maintenance and allows dynamic adaptation without code changes.
2. Performance Improvements
Version 2.0.0 introduces major optimizations across the request lifecycle:
- Reduced latency (approximately 50% improvement compared to v1.1.0 in secure mode)
- Improved throughput through better resource utilization
- Efficient caching when encryption is disabled
- Reduced redundant validation cycles for protected resources
These improvements make the platform more suitable for high-scale deployments.
3. Enhanced Database Architecture
The data layer has been significantly upgraded:
- PostgreSQL introduced as the primary relational database
- Continued support for Elasticsearch for search functionality
- Optional integration with ClickHouse for analytics (OLAP workloads)
Benefits:
- Better structured data handling
- Improved query performance
- Scalability for both transactional and analytical workloads
4. Optimized PDF Access Control
A new access model has been introduced for secure and efficient PDF delivery:
- Signature-based access validation
- Time-bound (expiration-based) access control
- Reduced need for repeated backend validation
Impact:
- Faster content delivery
- Lower backend load
- Improved security with controlled access windows
5. Improved System Design
Architectural improvements include:
- Removal of branch-based deployment strategy
- Introduction of feature flags for modular behavior
- Cleaner separation of concerns across services
This lays the groundwork for:
- CDN integration
- Read replicas
- Request batching
- Horizontal scaling
Security Model Changes
Security is now configurable rather than enforced universally.
Available security features:
- End-to-End Encryption (AES-GCM based)
- Request signing for integrity and replay protection
- Payload validation and sanitization
- Secure file inspection and verification
Important considerations:
- Security guarantees depend on enabled configurations
- Backend remains the sole enforcement layer for validation
- TLS-only deployments rely on HTTPS and are less secure than E2E mode
Performance vs Security Trade-offs
| Mode | Characteristics |
|---|---|
| Full Security Mode | Higher CPU usage, increased latency, maximum data protection |
| Hybrid Mode | Balanced performance and security |
| Performance Mode | Lower latency, higher throughput, reduced security overhead |
This flexibility allows deployments to be tailored for:
- Enterprise secure environments
- Public high-scale platforms
- Mixed workload systems
Comparison with v1.1.0
| Feature | v1.1.0 | v2.0.0 |
|---|---|---|
| Architecture | Branch-based | Configuration-driven |
| Encryption | Always enabled | Optional |
| Database | MongoDB | PostgreSQL + ClickHouse support |
| Performance | Limited under heavy load | Significantly improved |
| PDF Access | Validation-heavy | Signature + expiration-based |
| Scalability | Restricted | Extensible and modular |
Migration Notes
- Existing deployments must migrate environment configurations to use feature flags
- Database migration may be required when switching from MongoDB to PostgreSQL
- Security settings should be carefully reviewed to match deployment requirements
Conclusion
VayuReader v2.0.0 transforms the platform into a scalable, flexible, and production-ready system. By introducing configuration-based controls, improved database support, and optimized content delivery mechanisms, this release enables a wide range of deployment scenarios.
It is recommended as the default version for most use cases, offering a strong balance between performance, security, and maintainability.