Show HN: A Database Written in Golang

sure man

Looks fun, but the intro requirement is "Knows C++" - that's kinda a non starter right?

thank you for referring, feel free to ask any questions you may have

thanks man yes currently it is not a fully sql database (have to add query support) My fav part of code is the data retrieval code because had some issues there & got to know lot about it

Learnt about B+ Trees, transactions, managing concurrent reads & data presistence

You can use https://github.com/cockroachdb/cockroachdb-parser which is basically PGSQL compatible parser implemented in golang

yes man have to work on adding the sql cmd support thanks for the links

thanks for the suggestion man, will definitely think about this

will surely checkout thanks man

thanks man

I took a quick glance at the code, I believe it may build upon "Build Your Own Database From Scratch in Go" [0]. The first part of the book is available for free on the author's website, along with information on how to purchase the full book (which includes source code).

I share the same goal and am working through the material after working through Codecrafters' "Build your own SQLite" [1]. Good luck!

I apologize in advance for mistakes (formatting, et cetera). I just registered this account to point you toward resources I found helpful.

[0] https://build-your-own.org/database/

[1] https://app.codecrafters.io/courses/sqlite/overview

followed this book - https://build-your-own.org/database/

Here's my list (probably not all of them)

https://github.com/FireScroll/FireScroll/

https://github.com/danthegoodman1/DurableStreams (brand new)

https://github.com/danthegoodman1/ObjectKV

https://github.com/danthegoodman1/WriteAhead

https://github.com/danthegoodman1/icedb (most popular)

https://github.com/danthegoodman1/Percolators (kind of a DB on top of a DB, technically just transactions tho)

there are others that might not fit exactly what you're looking for

Hi Phil, I thought I'd find you here! Love your blog!

Nice, thanks! I didn‘t know there was a subreddit for that.

It does not seem to speak SQL:

    $ git clone git@github.com:Sahilb315/AtomixDB.git
    Cloning into 'AtomixDB'...
    $ cd AtomixDB/
    $ go run .
    Welcome to AtomixDB
    Available Commands:
      CREATE       - Create a new table
      INSERT       - Add a record to a table
      DELETE       - Delete a record from a table
      GET          - Retrieve a record from a table
      UPDATE       - Update a record in a table
      BEGIN        - Begin new transaction
      COMMIT       - Commit transaction
      ABORT        - Rollback transaction
      EXIT         - Exit the program
    
    > create
    Enter table name: foo
    Enter column names (comma-separated): bar,baz
    Enter column types (comma-separated as numbers): 1,2
    Enter indexes (format: col1+col2,col3, ... or leave empty):
    Table 'foo' created successfully.
    > get
    Enter table name: foo
    
    Select query type:
    1. Index lookup (primary/secondary key)
    2. Range query
    3. Column filter
    Enter choice (1, 2 or 3):

I do find the source to be well organized and quite readable. Especially if you runs the commands in the cli and then trace how they are each implemented.

it is kind of a sql db but currently does not have the query lang (sql lang) & data is stored in tables similar to other relational DBs. Still have a lot of stuff to add & fix Will add more detail to it

> Main focus was on implementing & understanding working the of database

I think this clearly describes what was the goal.

"Main focus was on implementing & understanding working the of database, storage management & transaction handling."

Obviously OP wrote it to understand database theory & implementation.

That a database written in an AOT compiled managed language is possible, for example.

Specially relevant, because it used to be that writing database engines used to be considered systems programming, and we all know managed languages cannot be possible used for such tasks. /s

It's hackernews, basically every old thing has to be reinvented in the "language of the week", be it go, rust, ruby, or whatever was before that.

From a learning perspective, nice project for OP, for 'advertising' it, i'd prefer the "what's better than the alternatives" instead of focusing on the language.