PumpkinDB

Data

database engine

SHOW HN2017

190points
48comments
#180of 2,242 in 2017
Top 9%of 2017 by points

How HN took it

CuriousMostly questions and neutral comments

8 positive, 13 neutral or asking, 0 mixed, 4 critical, out of 25 comments about the project. Thread score +0.18.

Idea: 4 for, 1 againstDocs: 1 for, 3 against

The thread, comment by comment

Each row is a top-level comment and its replies, in HN's order. Select a cell to open that comment on HN.

positive neutral or mixed critical about another commenter or something else the maker

What HN said

What people liked

  • Interesting design, low-level immutable DB engine as building block

    From 2 comments
    • I am a big fan of this approach: Low-level, high-performance, immutable-by-default database engine as a building block, with bindings to multiple languages for easy application…
      vtuulos on HN
    • Amazing looking project! I've been daydreaming about using LMDB's memory mapping to provide a flexible low level db primitive for quite a while, figuring a combo of erlang like…
      elcritch on HN
  • Commit message style is interesting

    From 2 comments
    • I like how every commit message is formatted as a problem and a solution: https://github.com/PumpkinDB/PumpkinDB/commits/master
      simonw on HN
    • What an interesting commit message format.
      JoelSanchez on HN

Objections

  • Documentation is unclear about what it is and how to use it

    From 3 comments
    • From what I see in the published documentation, it's way too early to make it "show HN". If I didn't know what event sourcing is, I couldn't make heads or tails of your daemon,…
      dozzie on HN
    • Thanks. I read the entire "Documentation" page and still didn't feel confident that I understood what this really was. "Event sourcing" to me implies that it's generating events.
      ams6110 on HN
    • Well, its a fancy word. Thats basically what I took away from it. Also, I agree, read the whole doc and took way longer to understand what it does. Clearly, they are smart, but…
      ziikutv on HN
  • Too early for Show HN

    From 1 comment
    • From what I see in the published documentation, it's way too early to make it "show HN". If I didn't know what event sourcing is, I couldn't make heads or tails of your daemon,…
      dozzie on HN
  • Unclear use case and advantages

    From 1 comment
    • What's an actual use-case for this? I am reading the documentation but still don't see why I should use it and what the actual advantages compared to current solutions are.
      nik736 on HN
  • Disk space cost of never overwriting data; need for data removal

    From 2 comments
    • I don't get this whole "never overwrite data" thing, including Datomic, for example. Isn't the disk space needed for these schemes enormous?
      fiatjaf on HN
    • I have reservations, too: it's important to be able to remove data even though disk is cheap. * Removing very old data is a reasonable hedge for user privacy. * Sometimes…
      solidsnack9000 on HN

Requests

  • Better documentation and usage examples

    From 2 comments
    • Well, its a fancy word. Thats basically what I took away from it. Also, I agree, read the whole doc and took way longer to understand what it does. Clearly, they are smart, but…
      ziikutv on HN
    • Very interesting! I think one thing that this would benefit from is a lot of usage examples, especially around pumpkinscript. I was reading recently about MUMPS and Caché and…
      makmanalp on HN
  • Support for Akka persistence

    From 1 comment
    • Looks very interesting. I'd love to use it once it supports Akka persistence. Is this on the roadmap?
      stonewhite on HN

Questions

  • How does it compare to FoundationDB, Datomic or Berkeley DB?

    From 3 comments
    • So basically something similar to FoundationDB?
      mindcrash on HN
    • It seems to serve approximately the same purpose as Berkeley DB.
      mtdewcmu on HN
    • This sounds like my (probably wrong/incomplete) understanding of Datomic?
      mattdeboard on HN
  • Storage layout and range query support

    From 1 comment
    • Very interesting! I think one thing that this would benefit from is a lot of usage examples, especially around pumpkinscript. I was reading recently about MUMPS and Caché and…
      makmanalp on HN

Alternatives named

  • FoundationDB

    From 1 comment
  • Datomic

    From 1 comment
    • This sounds like my (probably wrong/incomplete) understanding of Datomic?
      mattdeboard on HN
  • Berkeley DB

    From 1 comment
    • It seems to serve approximately the same purpose as Berkeley DB.
      mtdewcmu on HN
  • Kafka and Samza

    From 1 comment
    • Where would I use this in place of, say, Kafka and Samza?
      cestith on HN

Category, keywords, summaries and labels on this page were made by AI (Thread Reader v2) and not checked by hand. Each point links to the comments it came from.

Add a badge to your READMEShown on HackerShow
[![Shown on HackerShow](https://hackershow.org/badge.svg)](https://hackershow.org/show/13738051)