Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

jti blacklist #66

Open
code-raisan opened this issue Sep 6, 2024 · 1 comment
Open

jti blacklist #66

code-raisan opened this issue Sep 6, 2024 · 1 comment

Comments

@code-raisan
Copy link
Member

No description provided.

@code-raisan
Copy link
Member Author

Redisを裏で使ってBackchannelで処理すればクライアントは幸せ

サーバーレスとかでもRedisをリクエストに挟むことのパフォーマンス低下を調べる必要ありけり

リクエスト毎にDBに確認はパフォーマンス落ちそうって思うけど、そんなことはないのかな？

ベストプラクティスがわからん。

まあRedisでセッション管理してて何を言っているって感じだけど

どうなんだろうっていうところ。

HTTP -> Redisっていうのもわりとありなら結構セッション同期は楽かも

どれもこれもback channelがまともな選択肢ならば

ほんとに早めに調査する必要ありけり

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@code-raisan