goshawkdb

[goshawkdb @goshawkdb]

Good grief, I just rewatched my 2016 qcon talk. That's a complex talk! The same material in about triple the time might have made it a bit more approachable. Sorry!
(P.s. I might be coming back to life soon)

[goshawkdb @goshawkdb]

@andy_pavlo @dataease @fauna @InterBase @nuodb @RavenDB I actually can't remember why I called this GoshawkDB!
Ravens are super intelligent, so I like @RavenDB for that reason. Goshawk is of course a proper raptor that you can go hunting with. Not sure about all those other birds though.

[goshawkdb @goshawkdb]

@dgryski @chris_csguy Yes, exactly. And I read @dgryski 's blogs with interest a few weeks ago - many of those algs I want to look at in more detail. In the case of GoshawkDB, I'm able to generate as much entropy as I need. But some of those other algs may be more efficient anyway.

[goshawkdb @goshawkdb]

@EzraHoch There's a soak test in there too both for java & go clients iirc. Btree should appear with the next release for ordered traversal

[goshawkdb @goshawkdb]

@EzraHoch the root obj may only be changed on insert though so shouldn't be too bad. Check the collections repo - linear hash in there.

[goshawkdb @goshawkdb]

@EzraHoch the former. If an obj is not reachable from any root then the obj can never be accessed. See the data model page on website.

[goshawkdb @goshawkdb]

@EzraHoch but distributed parallel concurrent incremental GC is going to take some research and hard thinking to get right!

[goshawkdb @goshawkdb]

@EzraHoch they're not supported *yet*. They will be eventually. Given it's an object model, it feels like GC is the right way to go.

[goshawkdb @goshawkdb]

There are some pretty exciting developments on their way just at the moment. Looking forward to the next release!

[Golang News 📰 @golangnews]

GoshawkDB - a distributed, transactional, fault-tolerant object store #golang https://t.co/xbRVtFB6QH

[goshawkdb @goshawkdb]

@adriancolyer Interesting. Some of the definitions there raise further questions - no blocking, 1 response. Fairly sure GoshawkDB is SOW.

[goshawkdb @goshawkdb]

@rchatley I am however thinking about a "mugs for bugs" policy. But they're going to need to be meaty bugs...

[goshawkdb @goshawkdb]

@rchatley Alas no. It's just whatever's in the bags in the curry jar in the cupboard...

[goshawkdb @goshawkdb]

They're here! Such excellent tea too!

[goshawkdb @goshawkdb]

Due to a mistake in the build, GoshawkDB 0.3.1 is released. This is a server only release. Clients are unaffected. https://t.co/YsN5RzJuBf

[goshawkdb @goshawkdb]

If you'd like a talk on where GoshawkDB sits with some other data stores, and how to think about using GoshawkDB: https://t.co/vJlqAjb5AD

[Lobsters @lobsters]

GoshawkDB 0.3 released
https://t.co/qxpJ8eQl0B
https://t.co/LwNonDrveF #databases #distributed

[goshawkdb @goshawkdb]

@WAWilsonIV Ordering is strictly causal, which is captured by the VectorClocks from each obj in each txn. Unrelated txns proceed in parallel

[goshawkdb @goshawkdb]

@WAWilsonIV Every paxos instance is totally independent, & can start directly in phase 2. Grey + Lamport's "consensus on txn commit" paper

[goshawkdb @goshawkdb]

@WAWilsonIV You're welcome. Please do email me if you have questions - twitter is limiting for in depth technical discussions ;)