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.

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

Investigate storing TLS certificates in memory. #183

Open
2 tasks
kevmo opened this issue May 21, 2021 · 0 comments
Open
2 tasks

Investigate storing TLS certificates in memory. #183

kevmo opened this issue May 21, 2021 · 0 comments
Labels
Engineering Technology and Development Track Type: Robustness Tickets to improve the application, invisibly
Milestone

Comments

@kevmo
Copy link
Contributor

kevmo commented May 21, 2021

Description

Currently our application is using fs.readFileSync everytime we need our certificate. We could potentially speed our app up by loading the certificate into memory and reading it there.

Some additional context

Acceptance Criteria

  • Investigate whether the performance benefit of loading the certificate in memory is worth development effort.
  • If so, write code to load TLS certificate into memory rather than synchronously reading the file every time its needed.
@kalvinwang kalvinwang added the Engineering Technology and Development Track label May 24, 2021
@kalvinwang kalvinwang mentioned this issue Jun 7, 2021
1 task
@lomky lomky added this to the Low Priority milestone Sep 14, 2021
@lomky lomky added Type: Developer Experience Tickets that improve the developer environment or development process Type: Robustness Tickets to improve the application, invisibly and removed Type: Developer Experience Tickets that improve the developer environment or development process labels Dec 21, 2021
@kalvinwang kalvinwang changed the title Store TLS certificates in memory. Investigate storing TLS certificates in memory. Dec 30, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Engineering Technology and Development Track Type: Robustness Tickets to improve the application, invisibly
Projects
None yet
Development

No branches or pull requests

3 participants