go-cache VS buntdb

Compare go-cache vs buntdb and see what are their differences.

go-cache

An in-memory key:value store/cache (similar to Memcached) library for Go, suitable for single-machine applications. (by patrickmn)

buntdb

BuntDB is an embeddable, in-memory key/value database for Go with custom indexing and geospatial support (by tidwall)
Our great sponsors
  • InfluxDB - Power Real-Time Data Analytics at Scale
  • WorkOS - The modern identity platform for B2B SaaS
  • SaaSHub - Software Alternatives and Reviews
go-cache buntdb
8 7
7,762 4,357
- -
0.0 1.2
4 months ago 3 months ago
Go Go
MIT License MIT License
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.

go-cache

Posts with mentions or reviews of go-cache. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2023-08-18.
  • My first package in go. An in-memory cache package useful when creating multiple instances of the cache
    2 projects | /r/golang | 18 Aug 2023
    Why I am creating this package? There is an already existing memory cache package which creates (One Janitor for One Cache) So I am running into issues where many go routines are running in our use cases causing the application to crash due to some memory leakage in the library itself or maybe multiple timers running at same time casuing the issue. Also this is a very popular github library but just doesn't fits when I am creating many cache instances. So thought about creating one package by myself.
  • VCache vs Go-Cache
    4 projects | /r/golang | 4 Feb 2023
    I wrote a new library called VCache (https://github.com/microup/vcache). VCahce differs from go-cache (https://github.com/patrickmn/go-cache) by using a key of type "any" instead of a key of type "string". I compared the performance of both libraries on the main operations: Add, Get, and Delete.
  • Better Cache - A Lightning Fast Caching System with Full Text Search
    2 projects | /r/golang | 25 Aug 2022
    https://github.com/patrickmn/go-cache is a well known one. My cache module is for it's fast full text search thus I recommend only using mine if u are using a pre-set cache.
  • go-cache VS ccache - a user suggested alternative
    2 projects | 2 Apr 2022
  • Implement an in-memory cache in Golang
    2 projects | dev.to | 17 Jan 2022
    github.com - patrickmn/go-cache
  • Log4j RCE Found
    32 projects | news.ycombinator.com | 9 Dec 2021
    > when they went a year without a release.

    Cause these libraries depend on other libraries that are probably extremely out of date at that point and have their own security vulnerabilities.

    An example of a project that hasn't been dismissed as "abandoned", is https://github.com/patrickmn/go-cache because it explicitly doesnt have dependencies.

    So yeah, if you have a semi-complex library, a year without a release is abandoned.

  • In-memory caching solutions
    4 projects | /r/golang | 1 Feb 2021
    Though pretty simple but have a look at https://github.com/patrickmn/go-cache

buntdb

Posts with mentions or reviews of buntdb. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2023-07-15.
  • PostgreSQL: No More Vacuum, No More Bloat
    6 projects | news.ycombinator.com | 15 Jul 2023
    Experimental format to help readability of a long rant:

    1.

    According to the OP, there's a "terrifying tale of VACUUM in PostgreSQL," dating back to "a historical artifact that traces its roots back to the Berkeley Postgres project." (1986?)

    2.

    Maybe the whole idea of "use X, it has been battle-tested for [TIME], is robust, all the bugs have been and keep being fixed," etc., should not really be that attractive or realistic for at least a large subset of projects.

    3.

    In the case of Postgres, on top of piles of "historic code" and cruft, there's the fact that each user of Postgres installs and runs a huge software artifact with hundreds or even thousands of features and dependencies, of which every particular user may only use a tiny subset.

    4.

    In Kleppmann's DDOA [1], after explaining why the declarative SQL language is "better," he writes: "in databases, declarative query languages like SQL turned out to be much better than imperative query APIs." I find this footnote to the paragraph a bit ironic: "IMS and CODASYL both used imperative query APIs. Applications typically used COBOL code to iterate over records in the database, one record at a time." So, SQL was better than CODASYL and COBOL in a number of ways... big surprise?

    Postgres' own PL/pgSQL [2] is a language that (I imagine) most people would rather NOT use: hence a bunch of alternatives, including PL/v8, on its own a huge mass of additional complexity. SQL is definitely "COBOLESQUE" itself.

    5.

    Could we come up with something more minimal than SQL and looking less like COBOL? (Hopefully also getting rid of ORMs in the process). Also, I have found inspiring to see some people creating databases for themselves. Perhaps not a bad idea for small applications? For instance, I found BuntDB [3], which the developer seems to be using to run his own business [4]. Also, HYTRADBOI? :-) [5].

    6.

    A usual objection to use anything other than a stablished relational DB is "creating a database is too difficult for the average programmer." How about debugging PostgreSQL issues, developing new storage engines for it, or even building expertise on how to set up the instances properly and keep it alive and performant? Is that easier?

    I personally feel more capable of implementing a small, well-tested, problem-specific, small implementation of a B-Tree than learning how to develop Postgres extensions, become an expert in its configuration and internals, or debug its many issues.

    Another common opinion is "SQL is easy to use for non-programmers." But every person that knows SQL had to learn it somehow. I'm 100% confident that anyone able to learn SQL should be able to learn a simple, domain-specific, programming language designed for querying DBs. And how many of these people that are not able to program imperatively would be able to read a SQL EXPLAIN output and fix deficient queries? If they can, that supports even more the idea that they should be able to learn something different than SQL.

    ----

    1: https://dataintensive.net/

    2: https://www.postgresql.org/docs/7.3/plpgsql-examples.html

    3: https://github.com/tidwall/buntdb

    4: https://tile38.com/

    5: https://www.hytradboi.com/

  • Is there a nice embedded json db, like PoloDB (Rust) for Golang
    8 projects | /r/golang | 5 Nov 2022
    https://github.com/tidwall/buntdb -> i think this one you might want
  • Open Source Databases in Go
    52 projects | /r/golang | 8 Jun 2022
    buntdb - Fast, embeddable, in-memory key/value database for Go with custom indexing and spatial support.
  • Alternative to MongoDB?
    9 projects | /r/golang | 12 May 2022
    BuntDB for NoSQL
  • Path hints for B-trees can bring a performance increase of 150% – 300%
    3 projects | news.ycombinator.com | 30 Jul 2021
    BuntDB [0] from @tidwall uses this package as a backing data structure. And BuntDB is in turn used by Tile38 [1]

    [0] https://github.com/tidwall/buntdb

  • The start of my journey learning Go. Any tips/suggestions would greatly appreciated!
    6 projects | /r/golang | 29 Jun 2021
  • In-memory caching solutions
    4 projects | /r/golang | 1 Feb 2021
    I've used BuntDB and had a great experience with it. It's basically just a JSON-based key-value store. I'm a huge fan of the developers other work (sjson, gjson, jj, etc) and stumbled on it while looking for a simple, embedded DB solution. It's not specifically a cache, though--just a simple DB, so you'd have to write the caching logic yourself.

What are some alternatives?

When comparing go-cache and buntdb you can also consider the following projects:

BigCache - Efficient cache for gigabytes of data written in Go.

bolt

badger - Fast key-value DB in Go.

groupcache - groupcache is a caching and cache-filling library, intended as a replacement for memcached in many cases.

GCache - An in-memory cache library for golang. It supports multiple eviction policies: LRU, LFU, ARC

cache2go - Concurrency-safe Go caching library with expiration capabilities and access counters

nutsdb - A simple, fast, embeddable, persistent key/value store written in pure Go. It supports fully serializable transactions and many data structures such as list, set, sorted set.

go-memdb - Golang in-memory database built on immutable radix trees

goose

goleveldb - LevelDB key/value database in Go.