iamaleksey

7 ms·

1.
by iamaleksey 9y ago
Except they are. Catalogued as δ-CRDT, under Lexicographic Counter in https://arxiv.org/pdf/1603.01529.pdf edit: Although to be fair that blog post is ancient and covers Cassandra 2.0, now no longer supported. Counters
2.
by iamaleksey 12y ago
CQL is compatible with Thrift-created column families (the inverse is not true, though). Just do a DESCRIBE SCHEMA from cqlsh and see how CQL interprets a particular Thrift-created column family, then use regular INSERTs.
3.
by iamaleksey 13y ago
This is not true. See this for example: http://www.datastax.com/dev/blog/thrift-to-cql3 You can do CREATE TABLE schemaless (id blob, name blob, value blob, PRIMARY KEY (id, name)) WITH COMPACT STORAGE; and have a
4.
by iamaleksey 13y ago
> Cassandra is really awesome at writes but reads are really expensive This is getting old, and is just plain untrue. Reads are more expensive than the extremely cheap writes, but they really aren't expensive. > Atomicity at th
5.
by iamaleksey 13y ago
No batching here, just single-partition, two cell update. Atomic, but not isolated in the way you define isolation in your gist.
6.
by iamaleksey 13y ago
The difference is that all the cells with the same `id` would belong to the same partition and stored together, so you'd be able to write them atomically and read them together cheaply in a single operation. What marshray suggested wou
7.
by iamaleksey 13y ago
It's not how Riak does this, and it's not what's going on under the hood with Cassandra, either.
8.
by iamaleksey 13y ago
In case you are talking about Cassandra collections (maps and sets), and not abstract maps/sets, then you are wrong. Only CQL3 Lists work like that - there are no UUIDs anywhere in CQL3 maps/sets implementations.
9.
by iamaleksey 13y ago
Performance, mostly. To read both the email and the phone you'll have to make two requests (or a single multiget). The keys have a good chance of belonging to different replicas, too, and even if they don't, you are still going to
10.
Handling Disk Failures In Cassandra 1.2(datastax.com)
28 points by iamaleksey 14y ago|0 comments
11.
by iamaleksey 15y ago
This reminded me of "God Mode" ( http://qntm.org/godmode ).
12.
by iamaleksey 16y ago
'static' in C is the worst - it has 2 different meanings within the same language. Does anyone know the reason for this confusing design decision?
13.
9 Erlang pitfalls you should know about(mazenharake.wordpress.com)
2 points by iamaleksey 16y ago|0 comments
14.
by iamaleksey 16y ago
This is useful, thanks. Would be even better with RSS/Atom feed.
15.
by iamaleksey 16y ago
Also ejabberd.
16.
by iamaleksey 16y ago
SMS/MMS gateway (aggregator) with SMPP, CIMD and MM7 support and AMQP interface (RabbitMQ as a broker). Also building a simple SMSC right now. It's a perfect fit.
17.
Gproc - Erlang Global Process Registry(rklophaus.com)
20 points by iamaleksey 16y ago|2 comments
18.
by iamaleksey 17y ago
Is there even a word in japanese for "obscene"?
19.
by iamaleksey 17y ago
While Lua doesn't have many batteries included, it is trivial to expose a C lib-whatever interface to Lua when needed (example - http://github.com/iamaleksey/lua-zmq/blob/master/zmq.c ). And there is a c/++ library for almost everything.
20.
by iamaleksey 17y ago
There is also http://erlapi.prepor.ru/docs/
21.
Efene - a programming language with C-like syntax that runs on the erlang vm(github.com)
30 points by iamaleksey 17y ago|17 comments
22.
by iamaleksey 17y ago
ets:new(global_state, [set, public, named_table]) Now we've got a named table that any process may read or write to. It is possible.
23.
by iamaleksey 17y ago
Now that we have DHT + PEX + magnet links ( http://lifehacker.com/5411311/bittorrents-future-dht-pex-and... ), someone should come up with distributed torrent search and make the whole chain distributed.
24.
by iamaleksey 17y ago
Tsst, don't say things like this. They can be reading HN.
25.
JavaGems: gemcutter for the JVM(javagems.org)
29 points by iamaleksey 17y ago|7 comments
26.
by iamaleksey 17y ago
It will, but not anytime soon.
27.
by iamaleksey 17y ago
ASN.1 actually did take off, somewhat, at least in telco. And after comparing thrift to protobuffs to ASN.1 for our internal protocol I ended up chosing ASN.1, mostly because of the great ASN.1 support in the OTP (I'm using Erlang). Erlang
28.
by iamaleksey 17y ago
REST, Thrift, AMQP + protobuffs.
29.
by iamaleksey 17y ago
A standard might lead to slower innovation at this point.
30.
by iamaleksey 17y ago
There is STUNT for that, but I have no idea about its current status. [ http://nutss.gforge.cis.cornell.edu/stunt.php ] [ http://tools.ietf.org/html/draft-ietf-mmusic-ice-tcp-08 ].

More ›