Yes, though as your link points out, "The RAMP family is not designed to
provide ACID guarantees - it’s for situations where atomic reads are good
enough. Concurrent writes will typically be handled with last write wins or
CRDTs."
On Wed, Jan 16, 2019 at 1:04 PM Jonathan Haddad wrote:
> Sounds
Sounds a bit like RAMP: http://rustyrazorblade.com/post/2015/ramp-made-easy/
On Wed, Jan 16, 2019 at 12:51 PM Carl Mueller
wrote:
> "2) Overview: In essence, the protocol calls for each data item to
> maintain the last committed and perhaps also the currently active version,
> for the data and
"2) Overview: In essence, the protocol calls for each data item to maintain
the last committed and perhaps also the currently active version, for the
data and relevant metadata. Each version is tagged with meta-data
pertaining to the transaction that created it. This includes the
transaction
Hi,
Fanastic news!
Ariel
On Tue, Nov 13, 2018, at 10:36 AM, Hiroyuki Yamada wrote:
> Hi all,
>
> I am happy to release it under Apache 2 license now.
> https://github.com/scalar-labs/scalardb
>
> It passes not only jepsen but also our-built destructive testing.
> For jepsen tests, please
Hi all,
I am happy to release it under Apache 2 license now.
https://github.com/scalar-labs/scalardb
It passes not only jepsen but also our-built destructive testing.
For jepsen tests, please check the following.
https://github.com/scalar-labs/scalardb/tree/master/jepsen/scalardb
Also, as Yuji
Hi all,
Thank you for the comments and feedbacks.
As Jonathan pointed out, it relies on LWT and uses the protocol
proposed in the paper.
Please read the design document for more detail.
https://github.com/scalar-labs/scalardb/blob/master/docs/design.md
Regarding the licensing, we are thinking
Which was followed up by
https://www.researchgate.net/profile/Akon_Dey/publication/282156834_Scalable_Distributed_Transactions_across_Heterogeneous_Stores/links/56058b9608ae5e8e3f32b98d.pdf
On Tue, Oct 16, 2018 at 1:02 PM Jonathan Ellis wrote:
> It looks like it's based on this:
>
It looks like it's based on this:
http://www.vldb.org/pvldb/vol6/p1434-dey.pdf
On Tue, Oct 16, 2018 at 11:37 AM Ariel Weisberg wrote:
> Hi,
>
> Yes this does sound great. Does this rely on Cassandra's internal SERIAL
> consistency and CAS functionality or is that implemented at a higher level?
I think it does use LWT under the hood:
https://github.com/scalar-labs/scalardb/blob/master/src/main/java/com/scalar/database/transaction/consensuscommit/CommitMutationComposer.java#L74-L79
return new Put(base.getPartitionKey(), getClusteringKey(base,
result).orElse(null))
What License did you use? Can we please use Apache 2.0?
On Tue, Oct 16, 2018 at 9:39 AM sankalp kohli
wrote:
> This is awesome and thanks for working on it.
>
> On Tue, Oct 16, 2018 at 9:37 AM Ariel Weisberg wrote:
>
>> Hi,
>>
>> Yes this does sound great. Does this rely on Cassandra's
This is awesome and thanks for working on it.
On Tue, Oct 16, 2018 at 9:37 AM Ariel Weisberg wrote:
> Hi,
>
> Yes this does sound great. Does this rely on Cassandra's internal SERIAL
> consistency and CAS functionality or is that implemented at a higher level?
>
> Regards,
> Ariel
>
> On Tue,
Hi,
Yes this does sound great. Does this rely on Cassandra's internal SERIAL
consistency and CAS functionality or is that implemented at a higher level?
Regards,
Ariel
On Tue, Oct 16, 2018, at 12:31 PM, Jeff Jirsa wrote:
> This is great!
>
> --
> Jeff Jirsa
>
>
> > On Oct 16, 2018, at
This is great!
--
Jeff Jirsa
> On Oct 16, 2018, at 5:47 PM, Hiroyuki Yamada wrote:
>
> Hi all,
>
> # Sorry, I accidentally emailed the following to dev@, so re-sending to here.
>
> We have been working on ACID-compliant transaction library on top of
> Cassandra called Scalar DB,
> and are
Hi all,
# Sorry, I accidentally emailed the following to dev@, so re-sending to here.
We have been working on ACID-compliant transaction library on top of
Cassandra called Scalar DB,
and are pleased to announce the release of v.1.0 RC version in open source.
14 matches
Mail list logo
