Skip to content

Pravega Roadmap

The following will be the primary feature focus areas for our upcoming releases.

Version 0.9 (20Q4)

Version 0.10 (21Q2)

  • Spillover from 0.9
  • Separate LTS configurations per scope
  • Full AWS S3 support for LTS
  • Dynamic scaling (scale pods horizontally and vertically according to allocated resources and/or service demand)
  • Strengthen video streaming use-cases (#4087)
  • Segment Container load balancing (#1644)
  • Security-related enhancements
  • Quality-of-Service-related features
  • Support large events <=1GB (PDP 43, #5056)
  • Improve health checks (PDP 45, #5046, #5098)
  • Idempotent writer (#1210, #1437)
  • Performance improvements continued
  • Support config-based CDI and Spring client injection

Version 0.11

  • Spillover from 0.10
  • Refactor Tier-1
  • Native client bindings (phase 2: Golang)
  • QoS improvements continued
  • Performance improvements continued
  • Security enhancements continued

Version 0.12

  • Spillover from 0.11
  • Native client bindings (phase 3: Node.js, Ruby, C#)
  • Cross-site replication
  • QoS improvements continued
  • Performance improvements continued
  • Security enhancements continued
  • Edge functions
  • Shared namespace across Pravega clusters (between edge and core)
  • Pravega WebUI

Future Items

The following items are new features that we wish to build in upcoming Pravega releases, however many active work is currently underway. Please reach out on the Pravega channels if you're interested in picking one of these up.

  • Operational Features
    • Non-disruptive and rolling upgrades for Pravega
    • Provide default Failure Detector
    • Exposing information for administration purposes
    • Ability to define throughput quotas and other QoS guarantees
  • Pravega Connectors / Integration
    • Kafka API Compatibility (Producer and Consumer APIs)
    • Spark connectors (source/sink)
    • REST Proxy for Reader/Writer (REST proxy for Admin operations is already there)
  • Stream Management
    • Stream aliasing
    • Ability to assign arbitrary Key-Value pairs to streams - Tagging
  • Tiering Support
    • Policy driven tiering of Streams from Streaming Storage to Long-term storage
    • Support for additional Tier 2 Storage backends