Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

A database for 2022

tailscale.com

Post reply on HN
Print view View original

331–336 of 336 posts

Re: A database for 2022

#331

Post by rafiss »

IshKebab wrote: post #326
vvern wrote: post #256

Earlier quoted context omitted.

That’s not quite right. You can very much use the bsl code in production without a license and many, many companies do. The BSL contains a space for additional use grants. In crdb’s license, you can use the product for anything except building a hosted database as a service product. The definition of what that is is a little bit vague but it more or less means that the users of the product you sell shouldn’t be able…

You absolutely cannot use the BSL code in production without a commercial license. That's literally the first thing it says: > The Licensor hereby grants you the right to copy, modify, create derivative works, redistribute, and make non-production use of the Licensed Work. The Licensor may make an Additional Use Grant, above, permitting limited production use. Maybe specific software modifies that as you say, but the…

> The Licensor may make an Additional Use Grant, above, permitting limited production use.

See the text of the Additional Use Grant for CockroachDB [1]:

> Additional Use Grant: You may make use of the Licensed Work, provided that you may not use the Licensed Work for a Database Service.

> A “Database Service” is a commercial offering that allows third parties (other than your employees an contractors) to access the functionality of the Licensed Work by creating tables whose schemas are controlled by such third parties.

(disclaimer: I work at Cockroach Labs)

[1] - https://github.com/cockroachdb/cockroach/blob/master/license...

Re: A database for 2022

#332

Post by 0des »

stavros wrote: post #273
0des wrote: post #268

Earlier quoted context omitted.

As someone who was there to witness it when it happened, that is not the impression I got at all, and I think Dang may have taken the more humble interpretation in that remark.

You don't need to have been there, though, as anyone can read the perfectly-preserved exchange even now.

Lmao Stavros we should share a laptop or something or just speak over the phone the way we run in to each other so often.

Its different reading it at the time because it factors in the context of the community at the time as well as the lived experience of what it was like at the time to be a member or participant in given discussions. With that contrast, you can then get an idea of the intent of those comments beyond just the words, as they are often (and in this case) reinterpreted through the lens of current day contexts.

Example: ask what people think of the hit TV show The Apprentice today in the present, then hop in a delorean and ask someone before the trump presidency or candidacy what they think of the show.

Re: A database for 2022

#333

Post by stavros »

0des wrote: post #332
stavros wrote: post #273

Earlier quoted context omitted.

You don't need to have been there, though, as anyone can read the perfectly-preserved exchange even now.

Lmao Stavros we should share a laptop or something or just speak over the phone the way we run in to each other so often. Its different reading it at the time because it factors in the context of the community at the time as well as the lived experience of what it was like at the time to be a member or participant in given discussions. With that contrast, you can then get an idea of the intent of those comments beyon…

I guess that's true, the cultural context is different now.

You can call me anytime <3

Re: A database for 2022

#334

Post by jjeaff »

Aeolun wrote: post #41
jjeaff wrote: post #39

Earlier quoted context omitted.

I really hope they aren't taking the same tack when dealing with the encryption portion of their service.

What would be the analogue? Using openssl with a wrapper service? Doesn’t seem particularly dubious to me.

They have been trying to create or reinvent the database rather than using tried and true solutions. The analogue would be rolling your own cryptography.

Re: A database for 2022

#335

Post by Xeoncross »

tapirl wrote: post #104
Xeoncross wrote: post #3

Earlier quoted context omitted.

The litestream project was created by https://github.com/benbjohnson who wrote https://github.com/boltdb/bolt (a key value store) which has been instrumental (from my point of view) in the Go community as one of the original choices for an embedded database as it was not only fast, but had transactions with stable snapshots. It was used by https://github.com/blevesearch/bleve , https://github.com/etcd-io/etcd , and n…

It is strange that, although https://github.com/syndtr/goleveldb is used in the go-ethereum project for years, it is mentioned rarely (comparing to other go dbs).

Yes, it has it's own trade-offs, but is certainly a top-performer for certain workloads: https://github.com/smallnest/kvbench

Re: A database for 2022

#336

Post by odonnellryan »

bobnamob wrote: post #176
odonnellryan wrote: post #109

Earlier quoted context omitted.

You probably don't really want that. But not in the way that people didn't want WoW classic.

Can you elaborate on why you say this?

Because it would probably lead to the database doing stuff that you don't want it to do, with no way for you to tell it to do something else.
Post reply on HN