github.com/Xuanwo/storage
Package storage intend to provide a unified storage layer for Golang. - Production ready: high test coverage, enterprise storage software adaptation, semantic versioning, well documented. - High performance: more code generation, less runtime reflect. - Vendor agnostic: more generic abstraction, less internal details. There two main public interfaces: Servicer and Storager. Storager is a fully functional storage client, and Servicer is a manager of Storager instances, which will be useful for services like object storage. For any service, Storager is required to implement and Servicer is optional. The most common case to use a Storager service could be following: 1. Init a service. 2. Use Storager API to maintain data. - Storage uses error wrapping added by go 1.13, go version before 1.13 could be behaved as unexpected.
Readme
An application-oriented unified storage layer for Golang.
Basic operations
Extended operations
Multiple list style support
Segment/Multipart support
Required metadata
id: unique key in servicename: relative path towards service's work dirsize: size of this objectupdated_at: last update time of this objectOptional metadata
content-md5: md5 digest as defined in rfc2616content-type: media type as defined in rfc2616etag: entity tag as defined in rfc2616storage-class: object's storage class as defined in storage proposalimport (
"log"
"github.com/Xuanwo/storage"
"github.com/Xuanwo/storage/coreutils"
"github.com/Xuanwo/storage/types/pairs"
)
// Init a service.
store, err := coreutils.OpenStorager("fs", pairs.WithWorkDir("/tmp"))
if err != nil {
log.Fatalf("service init failed: %v", err)
}
// Use Storager API to maintain data.
r, err := store.Read("path/to/file")
if err != nil {
log.Printf("storager read: %v", err)
}
FAQs
Package storage intend to provide a unified storage layer for Golang. - Production ready: high test coverage, enterprise storage software adaptation, semantic versioning, well documented. - High performance: more code generation, less runtime reflect. - Vendor agnostic: more generic abstraction, less internal details. There two main public interfaces: Servicer and Storager. Storager is a fully functional storage client, and Servicer is a manager of Storager instances, which will be useful for services like object storage. For any service, Storager is required to implement and Servicer is optional. The most common case to use a Storager service could be following: 1. Init a service. 2. Use Storager API to maintain data. - Storage uses error wrapping added by go 1.13, go version before 1.13 could be behaved as unexpected.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
Cyber extortion in the US and Canada hit record levels in 2023, with ransomware attacks surging and median ransom demands skyrocketing, though fewer companies are choosing to pay ransoms.
Security News
Ecma TC39 is meeting this week and has moved key ECMAScript proposals forward, advancing Deferred Import Evaluation, Error.isError(), RegExp Escaping, and Promise.try to the next stages.
Security News
Researchers have demonstrated that teams of LLM agents can exploit zero-day vulnerabilities with a 53% success rate, and the costs of using AI to do so are rapidly becoming more affordable than hiring a human penetration tester.