The problem is that MySQL cannot meet the requirement of Google's growing needs of scalability and reliability. For the requirement of scalability, availability, consistency and usability, previous publications says they are mutually exclusive. F1 want to achieve these four "impossible" goals.
F1 is based on Spanner to enable the query.
The good performance of F1 is based on following difference from other related works.
1. Hierarchical Schema. In this schema, tables are organized into a hierarchy with child table rows, and interleaved within the rows of parent table
2. Table column contains protocol buffers.
3. Transactional fully consistent indices, which split into local indices and global indices
4. support for non-blocking schema
5 flexible lock granularity enabling.
For the shortcoming, F1 currently is not good for parallel query execution, which may needs fault recovery, isolation, etc.
I think it will still have impacts in next 10 years. Because it is the next generation of Google's NoSQL.

No comments:
Post a Comment