Shock is a platform to support computation, storage, and distribution. Designed from the ground up to be fast, scalable, fault tolerant, federated. (see Shock: Active Storage for Multicloud Streaming Data Analysis, Big Data Computing (BDC), 2015 IEEE/ACM 2nd International Symposium on, 2015)
Shock is RESTful. Accessible from desktops, HPC systems, exotic hardware, the cloud and your smartphone.
Shock is for scientific data. One of the challenges of large volume scientific data is that without often complex metadata it is of little to no value. Shock allows storage and querying of complex metadata.
Shock is a data management system. The long term goals of Shock include the ability to annotate, anonymize, convert, filter, perform quality control, and statically subsample at line speed bioinformatics sequence data. Extensible plug-in architecture is in development.
Shock is actively being developed at github.com/MG-RAST/Shock.
The fastest way to try Shock is with Docker Compose:
docker-compose up -d
curl http://localhost:7445/This starts Shock and MongoDB. See the tutorial for a hands-on walkthrough.
- Go 1.22+ (for building from source)
- MongoDB 3.6+ (metadata storage)
Use the provided build script, which sets the version from git tags:
./compile-server.shOr build directly with Go (note: vendored dependencies require -mod=vendor):
CGO_ENABLED=0 go install -mod=vendor -installsuffix cgo -v \
-ldflags="-X github.com/MG-RAST/Shock/shock-server/conf.VERSION=$(git describe --tags --long)" \
./shock-server/Pull the pre-built image:
docker pull mgrast/shockOr build it locally:
git clone https://github.com/MG-RAST/Shock.git
cd Shock
docker build -t mgrast/shock .To extract just the statically compiled binary from the image:
VERSION=$(docker run --rm mgrast/shock shock-server --version | grep version | grep -o v[0-9].* | tr -d '\n')
echo $VERSION
docker create --name shock mgrast/shock
mkdir -p bin
docker cp shock:/go/bin/shock-server ./bin/shock-server-${VERSION}
docker rm shockThe Shock configuration file uses INI format. A template is included at the root of the repository. Storage locations and node types are configured via Locations.yaml and Types.yaml respectively.
See the configuration guide for all options.
shock-server -conf <path_to_config_file>With Docker Compose (recommended):
docker-compose up -dThe default docker-compose.yml starts both Shock and MongoDB. For S3-compatible storage with MinIO, use the MinIO stack:
docker-compose -f docker-compose.minio.yml up -d shock-mongo shock-minio shock-minio-init shock-serverTests run in Docker with MongoDB:
# Run all tests
./run-tests.sh all
# Run tests for a specific package
./run-tests.sh package ./shock-server/node
# Generate coverage report
./run-tests.sh coverage
# Clean test environment
./run-tests.sh cleanFor S3 integration tests with MinIO:
docker-compose -f docker-compose.minio.yml up --abort-on-container-exit shock-test| Route | Description |
|---|---|
POST /node |
Create a new node (with or without file upload) |
GET /node/{nid} |
Retrieve node metadata |
GET /node/{nid}?download |
Download node file |
PUT /node/{nid} |
Update node attributes |
DELETE /node/{nid} |
Delete a node |
GET/PUT /node/{nid}/acl/ |
View or modify access control |
PUT /node/{nid}/index/{type} |
Create a file index |
GET/POST /node/{nid}/locations/ |
Manage storage locations |
GET /node?query&key=value |
Query nodes by metadata |
See the API documentation for full details and examples.
- Getting Started Tutorial
- Building Shock
- Configuration Guide
- Concepts
- API Reference
- Caching and Data Migration
- Data Types
- Use Cases
BSD-3-Clause