Grsql is a great tool to allow you set up your remote sqlite database as service and CRUD (create/ read/ update/ delete) it using gRPC.

Why Create This

Since I often use micro-service and database intergration is often required. for some "heavy" database like MySQL, MongoDB or something similar, it is a luxury to use them. A sqlite database with fast server backend would be a great solution for this.

This lead to the birth of Grsql.

How to Use

this project consist of two parts:

• server
• client

each part can run independently. the server normally run on remote/cloud side, the client make request to it.

use the following code run server,

cargo build --bin server

then the server starts listening on localhost port 7749.

on another side, to run client

cargo build --bin client 

It will insert the file's content input.txt into remote server, then read it, update its id and finally delete it.

Development

First of all, you need to be familiar with proto-buffer, if not, go to the site and see around.

since grsql is built on crates tonic, you need some pre-developing experience of rust, as well as tonic. see these examples to quick start.

you can modify/add/delete the message and service in proto/data.proto according to your requests then implement them according to that in src/server.rs

Notes

• No authentication implement so far

• gRPC is designed to deal with service that processes small and frequent communication, not for large file tranfer(file upload/download), if you do so, the performance is worse than HTTP2. It is better that the workload is less than 1M according to this, So use it with care!

you can refer these articles for more:

Sending files via gRPC

Upload/Download performance with gRPC

Use gRPC to share very large file

Feature to Add

• Add Athentication

Due to the issues mentioned above, it is desired to

• add a http2 module to handle large file upload/download.

To make transfer more efficient, it is resonable to

• add a compression