The emperor always intended to be naked. Naked is easy to clean. You never need to mend naked. Naked never goes out of style. Naked is chic.
-
-
Replying to @patio11
"Why the sudden enthusiasm for blockchains?" Options: a) You want to use the worst database in the world or b) justifies Bitcoin investment.
3 replies 26 retweets 29 likes -
Replying to @patio11
"Hang on Patrick, how can the database be the worst in the world? Isn't that hyperbole?" OK, let me pitch you on a new enterprise database:
1 reply 4 retweets 9 likes -
Replying to @patio11
Transaction processing times: theoretically unbounded, but we'll try for a poisson distribution averaging ~5 minutes for ACK, ~55 commit.
1 reply 1 retweet 5 likes -
Replying to @patio11
We'll support an append only log, and that's all. This will let clients have maximum freedom in how they interpret transaction history.
1 reply 2 retweets 4 likes -
Replying to @patio11
We'll support pretty complicated auth/auth for writing. For reads? Oh, we'll do the most common use case for databases: worldwide public.
1 reply 2 retweets 4 likes -
Replying to @patio11
Scaling? Heck yes, bring on the big data. We will support a blistering 1.7 kilobytes per second. Easily sufficient for worldwide use.
1 reply 3 retweets 6 likes -
Replying to @patio11
Durability and availability? We will almost never be unavailable for more than a few consecutive hours; less than 8 hours deleted per year.
1 reply 2 retweets 6 likes
Replication strategy: Hah, it's built in. No need for backups, sharding, or failover: we simply keep all data everywhere all the time.
-
-
Replying to @patio11
Library support: We have a single C++ codebase you have to be bug-for-bug compatible with. Alternative clients joining network may break it.
1 reply 2 retweets 9 likes -
Replying to @patio11
TCO: You may previously have used our competitor, Postgres, on a $3 a month server. Our requirements are similar; only 1 hydroelectric dam.
4 replies 7 retweets 29 likes - 1 more reply
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.