generated from finos/standards-project-blueprint
-
Notifications
You must be signed in to change notification settings - Fork 28
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
Initial version of the object store taxonomy #135
Merged
AdrianHammond
merged 5 commits into
finos:main
from
smendis-scottlogic:sm-object-storage-taxonomy
Mar 6, 2024
Merged
Changes from all commits
Commits
Show all changes
5 commits
Select commit
Hold shift + click to select a range
5b58095
initial version of the object store taxonomy
smendis-scottlogic 2b14a0d
updates
smendis-scottlogic 0bffd65
address review comments by stevie from scott logic and further improv…
smendis-scottlogic f98ba3e
addressed review comments by @rgriffiths-scottlogic
smendis-scottlogic f59f9e0
Signed URLs added
smendis-scottlogic File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,29 @@ | ||
# Object Storage Taxonomy | ||
|
||
This _service-level taxonomy_ documents the minimual set of features | ||
that should be present for a service to be considered portable for | ||
use in financial services ecosystems. | ||
|
||
## Taxonomy | ||
|
||
| Taxonomy ID | Feature | Description | | ||
| ----------- | ------- | ----------- | | ||
| CCC-020101 | Buckets | Concept of having uniquely identifiable containers in which objects exist. | | ||
| CCC-020102 | Metadata | Support storing, accessing, and managing of object metadata for stored objects. | | ||
| CCC-020103 | Scalability - Capacity Limit | Ability to store unlimited number of objects under a given maximum total capacity per bucket. | | ||
| CCC-020104 | Scalability - Object Size Limit | Ability to store large objects under a given maximum object size. | | ||
| CCC-020105 | Durability | High durability for stored objects through redundancy and replication. | | ||
| CCC-020106 | Availability | High availability for stored objects through replication over multiple (availability) zones within a region. | | ||
| CCC-020107 | Performance - Transaction Rate Limits | High throughput and low latency for read/write operations under given maximum transaction rate limits. | | ||
| CCC-020108 | Performance - Querying | Ability to perform simple select queries to retrieve only a subset of objects from the bucket. | | ||
| CCC-020109 | Storage Classes | Having different storage classes for frequently and infrequently accessed objects. | | ||
| CCC-020110 | Lifecycle Policies | Ability to define policies to automate data management tasks. | | ||
| CCC-020111 | Versioning | Ability to keep multiple versions of an object in the same bucket. | | ||
| CCC-020112 | Compliance and Governance | Ability to create locks on objects disabling modification and/or deletion of an object for a given period of time. | | ||
| CCC-020113 | Event Notifications | Publish object level events for creation, deletion and modification of objects allowing users to trigger actions in response. | | ||
eddie-knight marked this conversation as resolved.
Show resolved
Hide resolved
|
||
| CCC-020114 | Encryption at Rest | Data should be encrypted before storing by default. Should also make the option available for clients to maintain control over the encryptin keys. | | ||
| CCC-020115 | Encryption in Transit | Ability to encrypt data in transit using SSL/TSL. | | ||
| CCC-020116 | Identity Based Access Control | Ability to limit the users/roles who can access the object store. | | ||
| CCC-020117 | Object Level Access Control | Ability to control access to specific objects on the object store. | | ||
| CCC-020118 | Logging | Ability to log access, allowing the clients to track requests made to the object store. | | ||
| CCC-020119 | Signed URLs | Ability to give temporary access to objects and buckets through a signed URL or signed access token. | |
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This might imply there are only two classes of access: frequent and infrequent. However, there could be a few options between frequent and infrequent!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The 2 main category of classes should be hot (frequently accessed) and cold (infrequently accessed). We see more than 2 storage classes based on pricing. So it's ok?