akka/akka-http

Allow customized expiry time for cache entry

Open

#2,473 opened on Mar 17, 2019

View on GitHub
 (1 comment) (0 reactions) (0 assignees)Scala (598 forks)batch import
1 - triagedhackathonhelp wantedt:caching

Repository metrics

Stars
 (1,311 stars)
PR merge metrics
 (Avg merge 1d 10h) (2 merged PRs in 30d)

Description

We are building an aggregated services and using Akka Http Server to expose service endpoints and Akka Http Client to call underlying services. These underlying services require JWT based authentication. To maintain the token, we were thinking of using Akka Http Caching, but it seems it does not support dynamic expiry for cache entry which is required for JWT token.

Caffeine has provided a support for that. It would be a good idea to integrate it with Akka Http Caching. Thoughts?

Contributor guide

Research direction
Investigate how to integrate Caffeine's customizable expiry into Akka HTTP caching. Start by understanding the current caching implementation and Caffeine's Expiry interface.
Tech stack
scala
Domain
backend
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
3-5 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Mostly clear
Prerequisites
ScalaAkka HTTP
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
30