storj / eventkit

a go library for reporting multidimensional events over UDP

Storj V3 Network

Storj is building a distributed cloud storage network. Check out our white paper for more info!

---

Storj is an S3-compatible platform and suite of distributed applications that allows you to store data in a secure and distributed manner. Your files are encrypted, broken into little pieces and stored in a global distributed network of computers. Luckily, we also support allowing you (and only you) to retrieve those files!

Table of Contents

• Contributing
• Start using Storj
• License
• Support

Contributing to Storj

All of our code for Storj v3 is open source. If anything feels off, or if you feel that some functionality is missing, please check out the contributing page. There you will find instructions for sharing your feedback, building the tool locally, and submitting pull requests to the project.

A Note about Versioning

While we are practicing semantic versioning for our client libraries such as uplink, we are not practicing semantic versioning in this repo, as we do not intend for it to be used via Go modules. We may have backwards-incompatible changes between minor and patch releases in this repo.

Start using Storj

Our wiki has documentation and tutorials. Check out these three tutorials:

• Using the Storj Test Network
• Using the Uplink CLI
• Using the S3 Gateway

License

This repository is currently licensed with the AGPLv3 license.

For code released under the AGPLv3, we request that contributors sign our updated Contributor License Agreement (CLA) v2 so that we can relicense the code under Apache v2, or other licenses in the future.

Support

If you have any questions or suggestions please reach out to us on our community forum or file a ticket at https://support.storj.io/.

eventkit's Issues

evenkitd-bq daemon is broken

eventkit is allocating lots of heap

Profiling is showing lots of allocated heap for eventkit stuff

@elek said

We don't re-use buffers, I guess. And we send at least one message after each incoming DRPC request.
The real used memory should be lower....
But, yeah, some other things to improve....