owlcache

English | 中文简介

🦉owlcache is a lightweight, high-performance, non-centralized, distributed Key/Value in-memory Cache written in Go.It is an independent process and high-performance data middleware, and provides a variety of data get and import methods.You can query a node's key to get all the content with the same key in the node cluster. After operating the Key of a node, the data will be automatically synchronized to all node clusters.

Highlights and features

• 💡Cross-platform operation
• 🚀Single node ultra high performance
• ⛓Non-centralized, distributed
• 🌈Data concurrency security
• 🔍Support data expiration
• 🖥Key/Value Data storage
• 🎨Easy to use, only a few operating commands
• ⚔️Authentication
• 📝Logging
• 🔭Support TCP and HTTP/HTTPS, WebSocket (Search) connections
• 🍻Support Memcache、 Redis(String)、Url data import

Documentation

• 📝中文简体
• 📝English

Sub Project

🦌 deerfs:Using it, you can build a simple decentralized file system. Project address: deerfs

How to compile

go get -u github.com/xssed/owlcache

go build

./owlcache

owlcache

owlcache -help

Welcome to use owlcache. Version:XXX
If you have any questions,Please contact us: xsser@xsser.cc
Project Home:https://github.com/xssed/owlcache
                _                _
   _____      _| | ___ __ _  ___| |__   ___
  / _ \ \ /\ / / |/ __/ _' |/ __| '_ \ / _ \
 | (_) \ V  V /| | (_| (_| | (__| | | |  __/
  \___/ \_/\_/ |_|\___\__,_|\___|_| |_|\___|

Usage of owlcache:
  -config string
        owlcache config file path.[demo:/var/home/owl.conf] (default "owlcache.conf")
  -host string
        binding local host ip address. (default "0.0.0.0")
  -log string
        owlcache log file path.[demo:/var/log/] (default "./log_file/")
  -pass string
        owlcache Http connection password. (default "")

owlcache -config /var/home/owl.conf -host 127.0.0.1 -log /var/log/ -pass 1245!df2A

Simple use example

Single node to get the Key value

• TCP command: get <key>\n

get hello\n

• HTTP Note: HTTP access data is not verified by password, only other operations that change data require authentication.

http://127.0.0.1:7721/data/?cmd=get&key=hello

• Websocket command: get <key>

get hello

Response result example:

world

If it is an HTTP request, there will be Key details in the response message.
Key: hello
Keycreatetime: 2021-11-26 18:12:45.1932019 +0800 CST
Responsehost: 127.0.0.1:7721

Single node to get the Key value info

• TCP command: get <key> info\n

get hello info\n

• HTTP

owlcache version >= 0.4.2, http no longer supports 'info'

http://127.0.0.1:7721/data/?cmd=get&key=hello&valuedata=info

• Websocket command: get <key> info <Custom return string (not necessary, such as UUID)>

get hello info

or

get hello info 5c9eff00-3bed-4113-a095-2f3c771683d9

Response result example:

{
    "Cmd": "get",
    "Status": 200,
    "Results": "SUCCESS",
    "Key": "hello",
    "Data": "d29ybGQ=",
    "ResponseHost": "127.0.0.1:7721",
    "KeyCreateTime": "2021-11-09T14:12:36.8431596+08:00"
}

Attention to the HTTP Status code returned by the HTTP Request. please refer to the "Protocol" chapter.

The cluster obtains the Key value.

• Suppose there are now three owlcache HTTP services: 127.0.0.1: 7721, 127.0.0.1:7723, 127.0.0.1:7725. Each service has a data called Key called hello.

http://127.0.0.1:7721/group_data/?cmd=get&key=hello

Response result example:

world

The result obtained is the latest value of the update time in the cluster query.

The cluster obtains the key value information

http://127.0.0.1:7721/group_data/?cmd=get&key=hello&valuedata=info

Response result example:

[
    {
        "Address": "127.0.0.1:7721",
        "Data": "d29ybGQ=",
        "Key": "hello",
        "KeyCreateTime": "2021-11-26T18:12:45.1932019+08:00",
        "Status": 200
    },
    {
        "Address": "127.0.0.1:7723",
        "Data": "d29ybGQ=",
        "Key": "hello",
        "KeyCreateTime": "2021-11-12T11:34:53.0952566+08:00",
        "Status": 200
    },
    {
        "Address": "127.0.0.1:7725",
        "Data": "d29ybGQ=",
        "Key": "hello",
        "KeyCreateTime": "2021-11-11T11:34:53.0952522+08:00",
        "Status": 200
    }
]

The result is the information about which node in the cluster owns this Key.

...more please refer to the detailed description of the document

Design

FAQ

1.owlcache does not have master-slave mode. If a key is written to a node and the node crashes, then the key cannot be accessed?？

The author believes that the master-slave mode will occupy a lot of server resources and cause excessive data redundancy. It is recommended that important keys can be written to more than two nodes at the same time when setting, so that the access to keys is almost unaffected in the relative case. If all nodes in the cluster are down, it is really impossible to access the key.

Development and discussion(not involved in business cooperation)

• Email📪:xsser@xsser.cc
• Homepage🛀:https://www.xsser.cc