CASSEM is a distributed config management center, it is totally independent, so it's easy to deploy and maintain in your environment. At the
same time, it's deployed by Go which gives it platform-cross ability and fast-compile.
- HTTP Restful API to manage all configs
cassemadm.- Stateless so that it can be easily scaled.
- Gray released.
- Multi-version management.
- Operation log, each operation to config elements will be recorded.
- Permission control.
- Client instance management.
-
CTL/UItool support these are constructing oncassemadmRESTful API.
- Distributed storage component
cassemdb, based on raft consensus algorithm.- Master can read and write.
- Slave node can only respond to read request.
- Use
gRPCprotocol to communicate. -
WatchTTLfeatures support. -
Lazy Deletionthe expired KV. There is a deleting working thread to delete KV from queue, the queue's data is from two part, one isoperation check, another istimer check.
- Stateless agent component
cassemagentto improve client's usability.- Cache config elements, and using
LRU-Kreplacing algorithm. - Language independent support
HTTPandgRPCprotocol. - Client SDK, easy to use.
-
Change Pushability, gray released also built on this.
- Cache config elements, and using
Explanation:
- cassemdb provide KV storage capacity.
- cassemadm is the manager to whole cassem application.
- cassemagent‘s major duty is helping clients to access config easier, makes cassemdb work transparently to clients. Importantly, cassemagent is stateless so that it could easily scale up and load balance.
- cassemdb
The KV storage component in cassem, provide gRPC API.
The manager in cassem, provide RESTful API to communicate. It is serving for CTL and Dashboard UI.
Agent is serving for user's client, agent SDK, actually. Of course, agent is stateless server.
benchmark tested core RESTful API and try to optimize them, each benchmark test displays the final QPS result.