Move identities to a database #47

New Issue

Closed

opened 2022-01-07 09:58:37 +01:00 by pfm · 2 comments

pfm commented

2022-01-07 09:58:37 +01:00

Collaborator

We should:

measure performance of current solution (spawning a gpg process each time we need to encrypt a message) and
see if it doesn't limit our throughput. If it did, we could move identities to a database for faster lookup.

Options:

a key-value file database (Berkeley DB, gdbm, etc.);
a key-value / NoSQL database (Redis, Mongo);
a relational database (Maria DB, Postgresql).

We should: 1. measure performance of current solution (spawning a `gpg` process each time we need to encrypt a message) and 2. see if it doesn't limit our throughput. If it did, we could move identities to a database for faster lookup. Options: - a key-value file database (Berkeley DB, gdbm, etc.); - a key-value / NoSQL database (Redis, Mongo); - a relational database (Maria DB, Postgresql).