English | 中文简介

🦉owlcache

🦉owlcache is a lightweight, high-performance, non-centralized, distributed Key/Value memory-cached data sharing application written by Go (used as a lightweight database in certain scenarios).

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 both TCP and HTTP connections

Chinese use documentation

📝http://owl.xsser.cc

Original design intention

My first thought was to implement a data sharing application that would make it very easy to build an efficient data sharing cluster. The data in the cluster, they can be owned jointly, or a node can have other nodes to obtain at any time. All data in the cluster must first be "shared" and "accessible" data.

owl🦉 is clever and cute. Their heads range from 270°🦉.

How to compile

Compilation environment requirements

golang >= 1.9

Source download

Go command download (will automatically download the dependent library, if you directly download the source code will prompt the class library is missing)

go get -u github.com/xssed/owlcache

Open the owlcache home directory to execute the compile command

go build

Run

Note that the owlcache.conf file should be in the same directory as the main program

Linux

./owlcache

Windows (DOS)

Note: In the Windows production environment deployment, it is found that the memory release will be relatively slow after the query request processing, and will be released within about half an hour. Linux does not have this problem, which is related to Go's internal mechanism.

owlcache

Parameter help

You can check out the help before running.
Note that the runtime configuration parameters take precedence over the configuration parameters in the *.conf file.

owlcache -help

Welcome to use owlcache. Version:0.2
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 adress. (default "0.0.0.0")
  -log string
        owlcache log file path.[demo:/var/log/] (default "./log_file/")
  -pass string
        owlcache Http connection password. (default "shi!jie9he?ping6")

Example with configuration parameter run

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>

get hello

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

Request parameter	Parameter value
cmd	get
key	key name

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

Response result example:

{
    "Cmd": "get",
    "Status": 200,
    "Results": "SUCCESS",
    "Key": "hello",
    "Data": "world"
}

The cluster obtains the Key value.

Suppose there are now three owlcache 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.

Request parameter	Parameter value
cmd	get
key	key name

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