CacheCloud's five control planes, the numbers behind them, and the module layout you would extend
CacheCloud is a Redis private cloud platform from Sohu TV, supporting Standalone, Sentinel and Cluster architectures, effectively reducing large-scale Redis operations costs and improving resource management and utilization. The platform provides rapid setup/migration, operations management, elastic scaling, statistics monitoring and client integration.
At a glance
- What is it?
- CacheCloud is Sohu TV's Redis cloud management platform, built around Standalone, Sentinel and Cluster instances rather than around a Redis server. The README is short and Chinese first, so most of what a reader needs is spread across a wiki, an in-repo quickstart file, and the module names in the repository root.
- Who is it for?
- CacheCloud makes sense for a team already running many Redis instances across architectures and tired of provisioning them one machine at a time, since the value is in the shared control layer and the SDK access path. It does not fit a single Redis server on one box, and a reader who wants to verify the cost argument against cloud vendors will not find numbers in the repository text, since that comparison is an image.
- Can I use it commercially?
- Yes. Apache-2.0 is a permissive licence: you can use, modify and sell software built on it, as long as you keep its copyright and licence notices.
- Is it still maintained?
- Yes. The repository last received commits 9 days ago.
- What is it written in?
- Mainly HTML, according to GitHub's language statistics.
Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.
Star history
- sohutv/cachecloud9,024 ★ · -5
| Repository | 2026-09-22 | 2026-11-15 |
|---|---|---|
| sohutv/cachecloud | 9k | 9k |
-5 Stars in the last 54 days, measured from the daily GitHub snapshot. Compare with other projects
Editorial analysis
CacheCloud is a control plane around Redis, not a Redis server
CacheCloud is a Redis cloud management platform, published by Sohu TV under the Apache-2.0 licence. Its scope is the management layer: it supports the Standalone, Sentinel and Cluster architectures, and it exists to reduce the operating cost of Redis at scale and to improve how resources are allocated and used. The feature summary names rapid build and migration, operations management, elastic scaling, statistical monitoring, and client integration and access.
That division of labour is the thing to hold on to. CacheCloud provisions and watches Redis instances; it does not replace one, and it is not a drop-in library a client library talks to for caching. The client-facing pieces are an access path, with SDK access and language access listed as their own group.
For a reader this sets the size of the decision. A team with one Redis instance and one machine has nothing to orchestrate, and a platform that manages hundreds of instances solves a problem that team does not have. The architecture list is what tells you whether the platform applies at all: a mixed estate of Standalone, Sentinel and Cluster is the case it was built for, and the published scale section says how large that case gets in practice.
Five functional groups, and resource shrink sits inside the scaling one
The capability breakdown is grouped five ways rather than listed as a flat feature set. The deployment group covers host environment initialization, instance deployment and installation, and type plus architecture support. Operations management covers the host environment, resource management, application audit, application operations, quality monitoring and diagnostic analysis. Statistics and monitoring covers log collection, instance collection, machine collection, application statistics, monitoring and alerting, and problem diagnosis. Client access covers SDK access, language access and client monitoring. Elastic scaling covers resource shrink, application scaling and external access.
Two entries are worth pausing on. Resource shrink, sitting in the scaling group next to application scaling, says capacity reduction is treated as a first-class operation rather than something you do by hand when a machine is idle. And the monitoring group collects at three levels, log, instance and machine, alongside application statistics.
The limit here is documentation, not capability. The README names each item once and links out; it does not say which Redis versions, which Sentinel quorum settings or which cluster topologies the deployment group accepts. Those specifics have to come from the documentation pages, not from this list.
The scale figures describe one operator, not a benchmark
The platform publishes its own usage scale, and the numbers are specific enough to be worth reading closely: more than 80 billion commands a day, more than 18 TB of memory in total, more than 420 applications with more than 4800 instances, spread across more than 80 physical machines and more than 360 Kubernetes pods.
Read those as one company's operating footprint, not as a performance claim. They describe what a Redis estate looks like when it is large enough to need this kind of platform, which is a different statement from saying a given tool can handle a given load. There is no request rate, latency or memory-per-instance figure attached to them, and the platform is a management layer, so what is being counted is commands passing through Redis instances rather than work done by CacheCloud.
The practical use for a reader is sizing. Two numbers set the shape of the estate, more than 4800 instances and more than 420 applications, and one of them, more than 360 Kubernetes pods, tells you the deployment assumes container orchestration alongside bare machines. If your estate has tens of instances rather than thousands, these figures describe the problem the platform was built to solve and nothing more.
A Maven root with four modules, and no build instructions in the README
The repository root shows what this is made of: pom.xml at the top, then cachecloud-web, cachecloud-custom and redis-ecs as directories, plus the licence, the .github directory and three README files, README.md, README_CN.md and README_EN.md. The primary language recorded for the project is HTML, which fits a platform whose front end lives inside the web module rather than beside it.
A pom.xml at the root with named subdirectories is a Java project. That layout tells an extender where to work, but the README does not carry build or install commands, so there is nothing to copy from it. Getting a running instance starts with the documentation rather than with the repository text.
Versions are easier to read than the build. Releases are named 3.4, published on 8 June 2026, 3.3-v2 from 5 August 2024 and 3.3 from 26 June 2024, and the last push to the main branch is dated 8 June 2026, the same day as 3.4. The repository is not archived. Note the shape of that list: a two year gap between the 3.3 line and 3.4, with the V2 suffix marking the pre-release branch of the earlier version, so anything pinned to 3.3 is on a different code line from anything on 3.4.
The quickstart lives inside the web module, and the demo runs on a bare IP address
The links in the README are where the actual documentation sits, and two of them point at files committed inside the web module rather than at the wiki. The quickstart path is:
cachecloud-web/src/main/resources/static/wiki/quickstart/index.mdThe client access path sits beside it under access/client.md, and the wiki link covers the rest, with a separate anchor for frequently asked questions. There is also a live demo instance published at:
http://43.137.44.6:8080/admin/app/listA raw IP and port with no hostname is worth noticing before you build anything on it. It is an admin path, not a marketing page, and a demo on a bare address has no stated lifetime, no stated access control and no stated support commitment. Treat it as a look at the interface, not as a dependency.
For language, the top level README is the Chinese one and offers a switch to README_EN.md, while the documentation links above are single files shared by both. An English reader therefore has a translated README but a documentation set that is not duplicated, which is the practical gap in this project for non-Chinese speakers.
The comparison with cloud vendors is an image with a caption, not a table of costs
The README has a section comparing CacheCloud against cloud vendors, and its entire content is a caption naming Redis master-slave and cluster deployment cost above an image. There are no figures in the text, no pricing assumptions, no workload model, and no explanation of which cloud or which instance type the comparison assumes.
That is a real limit on what the repository can tell you. The most persuasive argument for a platform like this is usually economic, and here the economic argument is a picture whose numbers you would have to read off the image and then judge for yourself, against a cost model the project does not publish. A reader comparing self-managed Redis against a managed offering has to supply their own numbers on both sides.
The same restraint applies to the rest of the README. It is a landing page: architecture support, five functional groups, a usage scale, a demo link and contact details. Nothing in it is a benchmark, a throughput claim or a comparison you can quote in a decision, so the questions it leaves open, architecture coverage, build steps and cost, have to be answered from the documentation before you commit.
Support runs through chat groups, and the first QQ group is marked full
The contact section is a set of chat groups rather than an issue tracker or a support contract. Three QQ groups are listed, with the first marked as full and two more open, and there is a WeChat group as well. The WeChat note asks people who have public network resources to get in touch, so those resources can be added to the open source version's service deployment for trial use and improve everyone's experience.
For a reader, that defines what support means here. Questions get answered in a group, which is fine for a community and weak for anything with an expectation attached, because there is no ticket, no response target and no record that survives the chat scroll. The one tracked feedback path named in the README is a single issue, number 289, linked as Feedback.
Anyone evaluating this should decide early whether group-based support and a trial arrangement fit their environment, because the alternative channels the README offers are thin.
Editorial conclusion
CacheCloud makes sense for a team already running many Redis instances across architectures and tired of provisioning them one machine at a time, since the value is in the shared control layer and the SDK access path. It does not fit a single Redis server on one box, and a reader who wants to verify the cost argument against cloud vendors will not find numbers in the repository text, since that comparison is an image. Before adopting it, read the quickstart file in cachecloud-web, check which of the five functional groups your team would actually use, and confirm the release line you are pinning, because 3.4 shipped on 8 June 2026 after a two year gap from 3.3.
Frequently asked questions
How do you clear a cache in CacheCloud?
The README does not list a cache-clearing action; CacheCloud is a Redis management platform. Its five functional groups cover Redis deployment, operations management, statistics and monitoring, client access and elastic scaling.
Which Redis architectures does CacheCloud support?
Three: Standalone, Sentinel and Cluster. The platform is built around managing those architectures together for large scale Redis estates, with deployment, operations management, monitoring, client access and elastic scaling as the functional groups.
How large a Redis estate is CacheCloud built for?
The project publishes its own scale: more than 80 billion commands a day, more than 18 TB of memory in total, more than 420 applications and 4800 instances, across more than 80 physical machines and more than 360 Kubernetes pods. Those are one operator's numbers rather than a performance benchmark.
Official sources
Add this badge to your README
If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.
[](https://hysenlabs.com/projects/sohutv-cachecloud)Star history chart for your README
[](https://hysenlabs.com/projects/sohutv-cachecloud)Was this useful?