madflojo / hord Goto Github PK

Describe the idea

Hord needs to secure data to only those who should be creating/reading data. Ideally this should follow typical gRPC and HTTP authentication methods.

Describe possible implementations

At this point it seems that JWT and 2-way TLS are the most preferred solutions. Thought I think this needs a full design proposal including how authentication tokens should be managed within Hord.

Additional context

I do think that it makes sense to support multiple users/tokens and provide different privileges based on the user/token.

creating http call

Describe the bug
This project has no contributing guide. We should have one so people can contribute.

To Reproduce
Steps to reproduce the behavior:

1. Go to Github
2. See the lack of contributing guide

Expected behavior
Clear contributing guide that explains how to contribute to this project.

Describe the solution you'd like
It would be nice to be able to query Hord via REST calls as there may be cases where gRPC doesn’t fit with the clients needs.

Additional context

Ideally a HTTP requests should map as

• Get > Get
• Post > Set
• Put > Set
• Delete > Delete

The controls type should also be JSON.

Describe the idea

NATS has explicit KV support.

Describe possible implementations

here is one already: https://github.com/HeavyHorst/easykv/tree/master/nats

Additional context

NATS KV also has watch, so you can get an event what a KV item changes.

Is your feature request related to a problem? Please describe.
There is currently no way to query data or admin hord instances from command line.

Describe the solution you'd like
I think having a simple CLI as part of the hord package would be key. This CLI would be able to query using gRPC and admin Hord via a Admin API.

Additional context
My first thoughts are querying and admin functions but I think it would make sense for someone to propose a design via this issue before implementing.

Describe the idea

One thing folks are going to wonder, is how efficient is Hord. Best way to do that is to write some Benchmark tests and publish the results in the README.

Describe possible implementations

Write some benchmarks for various data sizes.