News for hackers. Stuff that matters.
Re:MongoDB 3.4.0-rc3 by aphyr on Tuesday February 07, 2017 @04:53PM (#13593218)
What does MongoDB bring that couldn't have 'built on top' of MySQL codebase, and used MySQL transational layer as it's underpinnings.

There are two challenges here. One is that MongoDB has a different data model than MySQL: hierarchical, schema-less documents instead of uniformly-typed flat tables. It's possible to map one to the other--look at Postgres' support for JSON datatypes. That involves extensions to both the storage format and query language, but it's certainly doable.

The bigger problem is that MySQL's local transactional isolation is nice, but not particularly helpful in a distributed context. Distributed transactions--even single-document ones--are still tough to implement correctly and efficiently. As an example, consider Percona XtraDB, or MySQL+Galera Cluster. Both are building on a serializable single-node system--but in a distributed context, they wind up failing to provide snapshot isolation, let alone serializability.

Re:MongoDB 3.4.0-rc3 by ClayFerguson on Tuesday February 07, 2017 @06:48PM (#13594222)
The point is that MongoDB writes/reads directly to File system. It could have been (and still could be retro-fitted) to ride on top of an RDBMS for all it's actual IO, and create a hybrid. I'm aware of all the orthogonal points you raised which have nothing to do with ruling out RDBMS as I/O
Re:MongoDB 3.4.0-rc3 by aphyr on Wednesday February 08, 2017 @12:52PM (#13600353)