Percona uses TokuDB Percona's "Getting to know TokuDB for MySQL" article is designed to promote TokuDB, but in fact, it also shows the history of MySQL...
As mentioned above, even if you do not use the transaction provided by InnoDB, its crash-safe nature is still one of the important factors for many people to choose InnoDB:
Even those that don't really need transactions rejoice in the crash resistance strength of InnoDB.
When I mention TokuDB later, I will mention the limit of the Fractal Tree Indexes resource structure to the current hardware architecture. In March this year, the English version of Wikipedia set up the Fractal tree index, which is still complete. Before that, I went to a video to learn about the features of this structure...
Percona currently stores TokuDB in beta and waits for GA to complete the operation again. In addition, it also wants to determine whether InnoDB table & TokuDB table can be used in the same transaction, this is important for zero-downtime migration. if it is not feasible, the project will be larger than the limit...