letsencrypt / letsencrypt/boulder
Improve order and authorization schema
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 5.8k
- Forks
- 649
- Avg merge
- 3d 23h
- Merged PRs (30d)
- 24
Description
Design goals:
- authorizations can have profiles associated with them, so we can control cross-profile authorization reuse
- tables should have a single primary key and no additional indices, to make them easy to migrate to key-value storage in the future
- tables should not have auto-increment IDs, to make them easy to migrate to sharded storage in the future
- the table containing (large, blobby) validation records should be append-only, rather than adding huge blobs to pre-existing rows in the authz table like we do today
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the authorization, profile, and validation-record schema definitions and their migration paths in the Boulder repository. Review how authorization reuse and validation records are currently stored; done means the schema satisfies the stated primary-key, non-auto-increment, profile-association, and append-only goals.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- databases
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100