Cachealot | Fully transactional , ditributed cache
kandi X-RAY | Cachealot Summary
kandi X-RAY | Cachealot Summary
Cachealot is a C# library. Cachealot has no bugs, it has no vulnerabilities and it has low support. You can download it from GitLab.
The project started years ago with the goal of creating a distributed cache that can process complex set queries and that is fully transactional (even for updates that impact multiple nodes). Caches with set queries (get many) need to manage the completion status of their data as they may contain only a subset of a database. In the case of Cachealot, once data is fed-in, an explicit declaration allows to specify the subset of data available. A "get many" request will return data only if it can guarantee that all data that can match the query is available. Of course it can also process simple queries by unique key as all classical caches. In this case it linearly scales up when the number of nodes increases. It provides a powerful linq provider. It achieved its goal. It is now used by some financial institutions in Paris (France). Recently we decided to use the very poweful query engine in order to develop a fully transactional NOSQL database. We are almost there, a pre release is imminent. As of now we are observing impressive performance With one single node around 50000 durable write (transactional) operations per second. And it linearly scales up with the number of nodes if you can afford only "one stage commit" transactions. "Two stage commit" transactions are also available with a cost in terms of response time which is as small as possible for a distributed transaction. Using an original approach to distributed transactions we can guarantee lock free distributed transactions. Only the nodes effectively involved in the transaction put other operations on wait during transaction and the lock is automatically released in case of failure.
The project started years ago with the goal of creating a distributed cache that can process complex set queries and that is fully transactional (even for updates that impact multiple nodes). Caches with set queries (get many) need to manage the completion status of their data as they may contain only a subset of a database. In the case of Cachealot, once data is fed-in, an explicit declaration allows to specify the subset of data available. A "get many" request will return data only if it can guarantee that all data that can match the query is available. Of course it can also process simple queries by unique key as all classical caches. In this case it linearly scales up when the number of nodes increases. It provides a powerful linq provider. It achieved its goal. It is now used by some financial institutions in Paris (France). Recently we decided to use the very poweful query engine in order to develop a fully transactional NOSQL database. We are almost there, a pre release is imminent. As of now we are observing impressive performance With one single node around 50000 durable write (transactional) operations per second. And it linearly scales up with the number of nodes if you can afford only "one stage commit" transactions. "Two stage commit" transactions are also available with a cost in terms of response time which is as small as possible for a distributed transaction. Using an original approach to distributed transactions we can guarantee lock free distributed transactions. Only the nodes effectively involved in the transaction put other operations on wait during transaction and the lock is automatically released in case of failure.
Support
Quality
Security
License
Reuse
Support
Cachealot has a low active ecosystem.
It has 0 star(s) with 0 fork(s). There are no watchers for this library.
It had no major release in the last 6 months.
Cachealot has no issues reported. There are no pull requests.
It has a neutral sentiment in the developer community.
The latest version of Cachealot is current.
Quality
Cachealot has no bugs reported.
Security
Cachealot has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.
License
Cachealot does not have a standard license declared.
Check the repository for any license declaration and review the terms closely.
Without a license, all rights are reserved, and you cannot use the library in your applications.
Reuse
Cachealot releases are not available. You will need to build from source code and install.
Top functions reviewed by kandi - BETA
kandi's functional review helps you automatically verify the functionalities of the libraries and avoid rework.
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of Cachealot
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of Cachealot
Cachealot Key Features
No Key Features are available at this moment for Cachealot.
Cachealot Examples and Code Snippets
No Code Snippets are available at this moment for Cachealot.
Community Discussions
No Community Discussions are available at this moment for Cachealot.Refer to stack overflow page for discussions.
Community Discussions, Code Snippets contain sources that include Stack Exchange Network
Vulnerabilities
No vulnerabilities reported
Install Cachealot
You can download it from GitLab.
Support
For any new features, suggestions and bugs create an issue on GitLab.
If you have any questions check and ask questions on community page Stack Overflow .
Find more information at:
Reuse Trending Solutions
Find, review, and download reusable Libraries, Code Snippets, Cloud APIs from over 650 million Knowledge Items
Find more librariesStay Updated
Subscribe to our newsletter for trending solutions and developer bootcamps
Share this Page