A non-blocking, multi-threaded high performance network library/framework on Linux. The cs in csnet stands for cattle shed. It uses one event loop per thread Reactor I/O mode and takes advantage of multi-cores.

There are two type of server models in CSNet: Middle Server Model and Edge Server Model.

        ┌────────────┐            ┌────────────┐            ┌────────────┐
        │edge server1│            │edge server2│            │edge server3│
        └────────────┘            └────────────┘            └────────────┘
               ▲                         ▲                         ▲
               │_________________________│_________________________│
                                         ▼
                               ┌──────────────────┐
                               │   middle server  │
                               └──────────────────┘
                                         ▲
                                         │
                                         ▼
                                  ┌────────────┐
                                  │   clients  │
                                  └────────────┘

A server model consist of a executable file (server) and a business module file (business_module.so). It's easy to write your own business logic codes.

If you found bugs in your business logic codes, or you need new business logic, just copy the new compiled business module (e.g, business_module.so.virsion) to the dir where you deployed it, there's a hot patching thread will detects (scan the dir and compare the md5sum) the new business module and hot patch the new business module without killing the process.

CSNet uses one request one response method to handle every request. Every request should receive a response within business_timeout seconds, or the related business timeout handler will be called.

• Kernel version >= 3.9
• gcc supports c99
• libssl-dev

• linked list
  • singly linked list
  • doubly linked list
• trees
  • binary search tree
  • red-black tree
• queue
• priority queue
• stack
• hash

• stack (based on tagged pointer + double-word cas)
• queue (based on hazard pointer + single-word cas)

• timing wheel timer

All the benchmark tests are test on virtual machine on my Macbook Pro.

• client send package to edge server, edge server send back the package to client
• server running on ubuntu 16.04, 2G RAM
• client running on ubuntu 14.04, 1G RAM
• test duration: 30 seconds
• package size: 128 bytes

• client send package to midd server, midd server send the package to edge server, edge server send back the package to midd server, then midd server send back the packge to client
• midd server running on ubuntu 16.04, 2G RAM
• edge server running on ubuntu 14.04, 2G RAM
• client running on ubuntu 14.04, 1G RAM
• test duration: 30 seconds
• package size: 128 bytes

$ cd csnet
$ make -j4

First, in order to make edge-servers and middle-servers to find each other, we must setup a service lookup server.

$ mkdir -p ~/csnet-bin/lookup-server && cd ~/csnet-bin/lookup-server
$ cp csnet/server/service-lookup/lookup-server csnet/server/service-lookup/*.sh csnet/server/service-lookup/*.conf csnet/business/edge-server-module/service-lookup/*.so ./

Modify the myip, myport and mytype in server.conf to yours.

$ mkdir -p ~/csnet-bin/edge-server && cd ~/csnet-bin/edge-server
$ cp csnet/server/edge-server/edge-server csnet/server/edge-server/*.sh csnet/server/edge-server/*.conf csnet/business/edge-server-module/edge-module-example/*.so ./

Modify the myip, myport and mytype in server.conf to yours, and modify sip and sport to the service lookup server's. And modify accept-server-type to the middle-server type if there's other middle-server want to connect to this edge-server.
Note: mytype must be the value in file csnet/libcsnet/csnet-service-type.h .

$ mkdir -p ~/csnet-bin/midd-server && cd ~/csnet-bin/midd-server
$ cp csnet/server/midd-server/midd-server csnet/server/midd-server/*.sh csnet/server/midd-server/*.conf csnet/business/midd-server-module/midd-module-example/*.so ./

Modify the myip, myport and mytype in server.conf to yours, and modify sip and sport to the service lookup server's. And modify connect-server-type to the edge-server type if there's this midd-server needs to connect edge-server.

$ mkdir -p ~/csnet-bin/ssl-server && cd ~/csnet-bin/ssl-server
$ cp csnet/server/ssl-server/ssl-server csnet/server/ssl-server/*.sh csnet/server/ssl-server/*.conf csnet/business/midd-server-module/midd-module-example/*.so ./

Modify the myip, myport and mytype in server.conf to yours, and modify sip and sport to the service lookup server's. And modify connect-server-type to the edge-server type if there's this midd-server needs to connect edge-server.

MIT

Copyright (c) 2015-2016 Lampman Yao