hbase-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Edward Capriolo <edlinuxg...@gmail.com>
Subject Re: Don't Settle for Eventual Consistency
Date Tue, 21 Feb 2017 03:24:27 GMT
On Mon, Feb 20, 2017 at 9:29 PM, Edward Capriolo <edlinuxguru@gmail.com>

> Ap systems are not available in practice..
> Cp systems can be made highly available.
> Sounds like they are arguing ap is not ap, but somehow cp can be ap.
> Then google can label failures as 'incidents' and cp and ap are unefected.
> I swear foundation db claimed it solved cap, too bad foundationdb is
> unavailableexception.
> On Friday, February 17, 2017, Ted Yu <yuzhihong@gmail.com> wrote:
>> Reference #8 at the end of the post is interesting.
>> On Fri, Feb 17, 2017 at 9:23 AM, Robert Yokota <rayokota@gmail.com>
>> wrote:
>> > Hi,
>> >
>> > This may be helpful to those who are considering the use of HBase.
>> >
>> > https://yokota.blog/2017/02/17/dont-settle-for-eventual-consistency/
>> >
> --
> Sorry this was sent from mobile. Will do less grammar and spell check than
> usual.

Totally fair comparison by the way. Call out figures with from Google and
Facebook, companies with huge development budgets and data centers, teams
with tends or hundreds of developers building in house software, then
compare those deployments to a deployment of Cassandra or Riak at

Random thought: Compare the availability of amazon S3, build to leverage
eventual consistency, on top of other systems with eventual consistency,
and compare that with say google cloud storage...

AvailableAll storage classes offer very high availability. Your data is
accessible when you need it. Multi-Regional offers 99.95% and Regional
storage offers 99.9% monthly availability in their Service Level Agreement.
Nearline and Coldline storage offer 99% monthly availability.

What happened to those 5 9s?

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message