[atombender]

The announcement is a little misleading — they're announcing two different things, not one:

* Scylla 3.0, which adds secondary indexes and materialized views; and

* OLTP and OLAP features, which are not ready.

I'm struggling to find any clear information on what's implied by OLTP, but from the roadmap [1], it looks like they're just adding Cassandra's LWTs, not ACID transactions. Last I heard, you couldn't build ACID on top of Cassandra/Scylla, since row updates across multiple keys cannot be done atomically. Calling this OLTP seems a little misleading.

[1] https://www.scylladb.com/product/technology/scylla-roadmap/

[mcms]

Actually, Scylla 3.0 is still RC [1] and as mentioned in the article will be released later this month.

And I don't think OLTP/OLAP is about LWTs. I think they are just talking about Scylla's ability to process normal updates in a timely manner while doing OLAP queries.

And you're right about ACID transactions. Multiple rows across two or more partitions can not be updated atomically, even with LWTs, but it is possible for a single partition.

[1] https://github.com/scylladb/scylla/releases

[atombender]

But OLTP is online transactional processing. Even with LWT, you arguably just can't do OLTP with Cassandra/Scylla, not without transactions.

[thdxr]

OLTP traditionally refers to the type of updates you do during normal use of your application. Frequent, small and incremental updates vs large sweeping reads and aggregations (OLAP)

The T does stand for transactional but in this context it is not referring to transactions in the database sense

[duarten]

[Scylla employee] We’re bootstrapping our LWT implementation now and we do want to take it much further, with multi-partition transactions.