[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"project-10465":3},{"id":4,"name":5,"fullName":6,"owner":7,"repo":5,"description":8,"homepage":9,"htmlUrl":10,"language":11,"languages":10,"totalLinesOfCode":10,"stars":12,"forks":13,"watchers":14,"openIssues":15,"contributorsCount":15,"subscribersCount":15,"size":15,"stars1d":15,"stars7d":16,"stars30d":17,"stars90d":15,"forks30d":15,"starsTrendScore":15,"compositeScore":18,"rankGlobal":10,"rankLanguage":10,"license":19,"archived":20,"fork":20,"defaultBranch":21,"hasWiki":20,"hasPages":20,"topics":22,"createdAt":10,"pushedAt":10,"updatedAt":28,"readmeContent":29,"aiSummary":30,"trendingCount":15,"starSnapshotCount":15,"syncStatus":31,"lastSyncTime":32,"discoverSource":33},10465,"redka","nalgeon\u002Fredka","nalgeon","Redis re-implemented with SQL","",null,"Go",4554,130,34,0,1,9,28.35,"BSD 3-Clause \"New\" or \"Revised\" License",false,"main",[23,24,25,26,27],"database","key-value","postgres","redis","sqlite","2026-06-12 02:02:22","\u003Cimg alt=\"Redka\" src=\"logo.svg\" height=\"80\" align=\"center\">\n\nRedka reimplements the core parts of Redis with SQL, while remaining compatible with Redis API.\n\nHighlights:\n\n- Data doesn't have to fit in RAM.\n- Supports ACID transactions.\n- SQL views for easier analysis and reporting.\n- Uses SQLite or PostgreSQL as a backend.\n- Runs in-process (Go API) or as a standalone server.\n- Implements Redis commands and wire protocol (RESP).\n\nRedka is stable and ready to use for testing and non-critical production scenarios. It's currently in maintenance mode, and no new features are planned.\n\n## Use cases\n\nHere are some situations where Redka might be helpful:\n\n_Embedded cache for Go applications_. If your Go app already uses SQLite or just needs a built-in key-value store, Redka is a natural fit. It gives you Redis-like features without the hassle of running a separate server. You're not limited to just get\u002Fset with expiration, of course — more advanced structures like lists, maps, and sets are also available.\n\n_Lightweight testing environment_. Your app uses Redis in production, but setting up a Redis server for local development or integration tests can be a hassle. Redka with an in-memory database offers a fast alternative to test containers, providing full isolation for each test run.\n\n_Postgres-first data structures_. If you prefer to use PostgreSQL for everything but need Redis-like data structures, Redka can use your existing database as the backend. This way, you can manage both relational data and specialized data structures with the same tools and transactional guarantees.\n\n## Commands\n\nRedka supports five core Redis data types:\n\n- [Strings](docs\u002Fcommands\u002Fstrings.md) are the most basic Redis type, representing a sequence of bytes.\n- [Lists](docs\u002Fcommands\u002Flists.md) are sequences of strings sorted by insertion order.\n- [Sets](docs\u002Fcommands\u002Fsets.md) are unordered collections of unique strings.\n- [Hashes](docs\u002Fcommands\u002Fhashes.md) are field-value (hash)maps.\n- [Sorted sets](docs\u002Fcommands\u002Fsorted-sets.md) (zsets) are collections of unique strings ordered by each string's associated score.\n\nRedka also provides commands for [key management](docs\u002Fcommands\u002Fkeys.md), [server\u002Fconnection management](docs\u002Fcommands\u002Fserver.md), and [transactions](docs\u002Fcommands\u002Ftransactions.md).\n\n## Installation and usage\n\nRedka comes in two flavors:\n\n- Standalone Redis-compatible server: [installation](docs\u002Finstall-standalone.md), [usage](docs\u002Fusage-standalone.md).\n- Go module for in-process use: [installation](docs\u002Finstall-module.md), [usage](docs\u002Fusage-module.md).\n\nYou can also run an [in-process Redka server](example\u002Fserver\u002Fmain.go) as a lightweight alternative to Redis test containers, or as a small-scale production instance.\n\n## Storage\n\nRedka can use either SQLite or PostgreSQL as its backend. It stores data in a [relational database](docs\u002Fpersistence.md) with a simple schema and provides views for better introspection.\n\n## Performance\n\nRedka is not about raw performance. You can't beat a specialized data store like Redis with a general-purpose relational backend like SQLite. However, Redka can still handle tens of thousands of operations per second, which should be more than enough for many apps.\n\nSee the [benchmarks](docs\u002Fperformance.md) for more details.\n\n## Contributing\n\nContributions are welcome. For anything other than bugfixes, please first open an issue to discuss what you want to change.\n\nMake sure to add or update tests as needed.\n\n## Acknowledgements\n\nRedka would not be possible without these great projects and their creators:\n\n- [Redis](https:\u002F\u002Fredis.io\u002F) ([Salvatore Sanfilippo](https:\u002F\u002Fgithub.com\u002Fantirez)). It's such an amazing idea to go beyond the get-set paradigm and provide a convenient API for more complex data structures.\n- [SQLite](https:\u002F\u002Fsqlite.org\u002F) ([D. Richard Hipp](https:\u002F\u002Fwww.sqlite.org\u002Fcrew.html)). The in-process database powering the world.\n- [Redcon](https:\u002F\u002Fgithub.com\u002Ftidwall\u002Fredcon) ([Josh Baker](https:\u002F\u002Fgithub.com\u002Ftidwall)). A very clean and convenient implementation of a RESP server.\n\nLogo font by [Ek Type](https:\u002F\u002Fektype.in\u002F).\n\n## Support\n\nRedka is mostly a [one-man](https:\u002F\u002Fantonz.org\u002F) project. It's currently in maintenance mode, and no new features are planned.\n","Redka 是一个用 SQL 重新实现的 Redis 核心功能项目，同时保持与 Redis API 的兼容性。其主要技术特点包括支持 ACID 事务、提供 SQL 视图以方便数据分析和报告，并可选择 SQLite 或 PostgreSQL 作为后端存储，数据不必全部放入内存中。Redka 支持五种核心 Redis 数据类型（字符串、列表、集合、哈希表、有序集合）以及键管理和事务命令。适用于 Go 应用程序嵌入式缓存、轻量级测试环境或偏好使用 PostgreSQL 来管理关系型数据及特殊数据结构的场景。该项目稳定可靠，适合用于测试及非关键生产环境。",2,"2026-06-11 03:28:41","top_topic"]