Lately, I have been playing a lot with my ETCD-Layer that is using the Record-Layer. Thanks to it, I was able to bootstrap my ETCD-layer very quickly, but I was not using a tenth of the capacities of this library. So I decided to go deeper. What would a gRPC abstraction of the Record-Layer look like? I’m very happy to opensource the Record-Store
You can find more infos on the Github Pages, it is packaging all the great things about the RL and exposing them through gRPC(and soon GraphQL) with multi-tenancy, encryption and security enabled.
It was design to enable such workflow for the developers:
- Opening KeySpace, for example
- Create a protobuf definition which will be used as schema
- Upsert schema
- Push records
- Query records
- Delete records
You need another KeySpace to store another type of data, or maybe a KeySpace dedicated for a dev environment? Juste open it and you are good to go!
Work is far from done, but I think it has reached the point where it can be seen. Next steps are working on GraphQL and clients.
Thanks again for RL’s developers to release such a library, I’m having a lot of fun playing with it despite 2020.