Roadmap

Overview

Our public roadmap outlines the high level direction we are working towards. We update this document when our priorities change: security and stability are our top priority.

Key areas

Security and operational excellence take precedence above all else. This means bug fixing, stability, customer's support, and internal compliance may delay one or more key areas below.

We may choose to re-prioritize or defer items based on customer feedback, security, and operational impacts, and business value.

Release Security (p0)

Our top priority is to establish the processes and infrastructure needed for a fully automated and secure end-to-end release process of new versions to Maven Central.

• Implement GitHub workflows and create infrastructure to release to Maven Central
• Implement end-to-end tests
• Implement OpenSSF Scorecard

v2 Release: Consistency and Ecosystem (p1)

As part of a new major version v2 release, we prioritize the Java project's consistency of core utilities (Logging, Metrics, Tracing) with the other runtimes (Python, TypeScript, .NET). Additionally, we will focus on integrating the library with popular technologies and frameworks from the Java and AWS ecosystem. Particularly, we aim at leveraging new techniques to allow customers to reduce Lambda cold-start time. The v2 release will also drop support for Java 8 moving to Java 11 as the baseline.

Core Utilities

• Review public interfaces and reduce public API surface area
• Release Logging v2 module
• Support high resolution metrics

Ecosystem

• Add GraalVM support
• Implement priming using CRaC to improve AWS Snapstart support
• Evaluate integration with popular Java frameworks such as Micronaut, Spring Cloud Function, or Quarkus

Other

• Validation module integration with HTTP requests
• Support validation module from within the batch module
• Documentation: Review and improve documentation to be consistent with other runtimes

Feature Parity (p2)

If priorities p0 and p1 are addressed, we will also focus on feature parity of non-core utilities. This allows customers to achieve better standardization of their development processes across different Powertools runtimes.

• Re-evaluate if there is a need for adding a lightweight customer Powertools event handler
• Add Feature Flags module
• Add S3 Streaming module
• Add support for Data Masking during JSON serialization

Missing something?

You can help us prioritize by upvoting existing feature requests, leaving a comment on what use cases it could unblock for you, and by joining our discussions on Discord.

Roadmap status definition

graph LR
    Ideas --> Backlog --> Work["Working on it"] --> Merged["Coming soon"] --> Shipped

Visual representation

Within our public board, you'll see the following values in the Status column:

• Ideas. Incoming and existing feature requests that are not being actively considered yet. These will be reviewed when bandwidth permits.
• Backlog. Accepted feature requests or enhancements that we want to work on.
• Working on it. Features or enhancements we're currently either researching or implementing it.
• Coming soon. Any feature, enhancement, or bug fixes that have been merged and are coming in the next release.
• Shipped. Features or enhancements that are now available in the most recent release.

Tasks or issues with empty Status will be categorized in upcoming review cycles.

Process

graph LR
    PFR[Feature request] --> Triage{Need RFC?}
    Triage --> |Complex/major change or new utility?| RFC[Ask or write RFC] --> Approval{Approved?}
    Triage --> |Minor feature or enhancement?| NoRFC[No RFC required] --> Approval
    Approval --> |Yes| Backlog
    Approval --> |No | Reject["Inform next steps"]
    Backlog --> |Prioritized| Implementation
    Backlog --> |Defer| WelcomeContributions["help-wanted label"]

Visual representation

Our end-to-end mechanism follows four major steps:

• Feature Request. Ideas start with a feature request to outline their use case at a high level. For complex use cases, maintainers might ask for/write a RFC.
• Maintainers review requests based on project tenets, customers reaction (👍), and use cases.
• Request-for-comments (RFC). Design proposals use our RFC template to describe its implementation, challenges, developer experience, dependencies, and alternative solutions.
• This helps refine the initial idea with community feedback before a decision is made.
• Decision. After carefully reviewing and discussing them, maintainers make a final decision on whether to start implementation, defer or reject it, and update everyone with the next steps.
• Implementation. For approved features, maintainers give priority to the original authors for implementation unless it is a sensitive task that is best handled by maintainers.

See Maintainers document to understand how we triage issues and pull requests, labels and governance.

Disclaimer

The Powertools for AWS Lambda (Java) team values feedback and guidance from its community of users, although final decisions on inclusion into the project will be made by AWS.

We determine the high-level direction for our open roadmap based on customer feedback and popularity (👍🏽 and comments), security and operational impacts, and business value. Where features don’t meet our goals and longer-term strategy, we will communicate that clearly and openly as quickly as possible with an explanation of why the decision was made.

FAQs

Q: Why did you build this?

A: We know that our customers are making decisions and plans based on what we are developing, and we want to provide our customers the insights they need to plan.

Q: Why are there no dates on your roadmap?

A: Because job zero is security and operational stability, we can't provide specific target dates for features. The roadmap is subject to change at any time, and roadmap issues in this repository do not guarantee a feature will be launched as proposed.

Q: How can I provide feedback or ask for more information?

A: For existing features, you can directly comment on issues. For anything else, please open an issue.