You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+6-5Lines changed: 6 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -33,11 +33,7 @@ Make use of the client by importing it in your Go client source code. For exampl
33
33
34
34
Unitdb supports Get, Put, Delete operations. It also supports encryption, batch operations, and writing to wildcard topics. See [usage guide](https://github.com/unit-io/unitdb/tree/master/docs/usage.md).
35
35
36
-
Samples are available in the examples directory for reference. To build unitdb client from latest source code use "replace" in go.mod to point to your local module.
37
-
38
-
```golang
39
-
go mod edit -replace github.com/unit-io/unitdb-go=$GOPATH/src/github.com/unit-io/unitdb-go
40
-
```
36
+
Samples are available in the examples directory for reference.
41
37
42
38
## Clustering
43
39
To bring up the Unitdb cluster start 2 or more nodes. For fault tolerance 3 nodes or more are recommended.
@@ -49,6 +45,11 @@ To bring up the Unitdb cluster start 2 or more nodes. For fault tolerance 3 node
49
45
50
46
Above example shows each Unitdb node running on the same host, so each node must listen on different ports. This would not be necessary if each node ran on a different host.
51
47
48
+
## Client Libraries
49
+
Make use of officially supported client libraries to connect to unitdb server running on single node and running on a cluster.
50
+
-[unitdb-go](https://github.com/unit-io/unitdb-go) Lightweight and high performance unitdb Go client library.
51
+
-[unitdb-dart](https://github.com/unit-io/unitdb-dart) High performance unitdb Flutter/Dart client library.
52
+
52
53
## Architecture Overview
53
54
The unitdb engine handles data from the point put request is received through writing data to the physical disk. Data is compressed and encrypted (if encryption is set) then written to a WAL for immediate durability. Entries are written to memdb and become immediately queryable. The memdb entries are periodically written to log files in the form of blocks.
Copy file name to clipboardExpand all lines: docs/utp.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -45,7 +45,7 @@ An application transport the data by uTP across network, it contains payload dat
45
45
### Client
46
46
A Client opens the network connection to the Server using TCP/IP, WebSocket, GRPC or other bi-direction network protocols.
47
47
- Pubslihes Application Mesasges to a topic that other Clients subscribes to.
48
-
- Sends a relay request to retrieve persisted Application Messages from Server.
48
+
- Sends a relay request to retrieve Application Messages persisted on Server.
49
49
- Subscribes to a topic to receive Application Messages.
50
50
- Unsubcribe to remove a topic subscription.
51
51
- Closes the network connection to the Server.
@@ -284,7 +284,7 @@ The PublishMessage contains folowing fields:
284
284
A publisher can specify time to-live (TTL) when publishing an Application Message.
285
285
286
286
### RELAY - Relay request
287
-
The RELAY Message is sent from the Client to the Server to get persisted Application Messages from server for one or more topics. Each Relay request pairs the topics with last durations. The Server sends PUBLISH Messages to the Client to forward Application Messages that were persisted by the Server for the Topics that match these Relay requests. The RELAY Message also specifies (for each request) the Last duration for which the Server can send persisted Application Messages to the Client.
287
+
The RELAY Message is sent from the Client to the Server to get Application Messages persisted on server for one or more topics. Each Relay request pairs the topics with last durations. The Server sends PUBLISH Messages to the Client to forward Application Messages that were persisted by the Server for the Topics that match these Relay requests. The RELAY Message also specifies (for each request) the Last duration for which the Server can send stored Application Messages to the Client.
288
288
289
289
The payload contains following fields.
290
290
@@ -301,7 +301,7 @@ The RelayRequest contains folowing fields:
301
301
| Last | string |
302
302
303
303
#### Last
304
-
A Client can specify Last duration (for example "1h") to retrive persisted Application Messages published to the Topic.
304
+
A Client can specify Last duration (for example "1h") to retrive Application Messages published to the Topic.
305
305
306
306
### SUBSCRIBE - Subscribe request
307
307
The SUBSCRIBE Message is sent from the Client to the Server to create one or more Subscriptions. Each Subscription registers one or more Topics for a Client. The Server sends PUBLISH Messages to the Client to forward Application Messages that were published to Topics that match these Subscriptions. The SUBSCRIBE Message also specifies (for each Subscription) the Delivery Mode with which the Server can send Application Messages to the Client.
0 commit comments