by Zardosht.Kasheff | Nov 27, 2013 | MySQL
This past Wednesday, I attended a talk at the Washington DC MongoDB User Group given by John Schulz, a chief architect at AOL. In the talk, TokuMX VS MongoDB Bake Off Based on a Primary AOL Use case, he describes his experiments comparing TokuMX with MongoDB for his...
by Dave Rosenlund | Nov 19, 2013 | MySQL
You love MongoDB for its ease of deployment – but are you worried about how your application will perform when it starts to scale? SPEAKER: Tim Callaghan, VP of Engineering at Tokutek DATE: Wednesday, November 20th TIME: 1pm ET Register Now! Join this...
by Zardosht.Kasheff | Nov 7, 2013 | MySQL
From the application’s perspective, TokuMX behaves very similarly, if not identically, to MongoDB in many ways. But in one subtle yet important way, on non-sharded clusters, TokuMX is different. With MongoDB, operations on each single document are transactional. With...
by Zardosht.Kasheff | Oct 31, 2013 | MySQL
Since our initial release last summer, TokuMX has supported fully ACID and MVCC multi-statement transactions. I’d like to take this post to explain exactly what we’ve done and what features are now available to the user. But before beginning, an important note: we...
by Leif.Walsh | Oct 24, 2013 | MySQL
Getting ready for tomorrow’s MongoDB Boston conference (come say hi if you see us!), I’m spending some time thinking about a post last week by Bryce Nyeggen: The Genius and Folly of MongoDB. It hits home in a lot of ways for me and the whole TokuMX team, because it...
by Alexander Rubin | Oct 23, 2013 | MySQL, Percona Events, Percona Live
The upcoming Percona Live London conference, November 11-12, features quite a number of talks about the latest MySQL features and related technologies. There will be a lots of talks about the new MySQL 5.6 features: Opening keynote highlights MySQL 5.6 new features....
by Stephane Combaudon | Oct 22, 2013 | MongoDB, MySQL
We already discussed one to one relations in MongoDB, and the main conclusion was that you should design your collections according to the most frequent access pattern. With one to many relations, this is still valid, but other factors may come into play. Let’s...
by Tim.Callaghan | Oct 18, 2013 | MySQL
Tokutek is pleased to announce today’s release of TokuMX v1.3. The goal of this release was to bring full MongoDB v2.4 compatibility (with the noted exception of Text Search and Geospatial Indexes). The initial release of TokuMX was based on MongoDB v2.2, but...
by Dave Rosenlund | Oct 16, 2013 | MySQL
Tokutek is proud to be a sponsor of the MongoDB Boston 2013 event in Boston next Friday, October 25. The annual one-day conference is dedicated to MongoDB and is featuring all new advanced sessions this year. A few things to look forward to according to...
by Zardosht.Kasheff | Oct 11, 2013 | MySQL
Since introducing TokuMX, we’ve discussed benefits that TokuMX has for existing MongoDB applications that require no changes. In this post, I introduce an extension we’ve made to the indexing API: clustering indexes, a tool that can tremendously improve query...
by Dave Rosenlund | Sep 25, 2013 | MySQL
Save Time & Money – Do It Right The First Time SPEAKER: Tim Callaghan, VP Engineering, Tokutek DATE: Thursday, September 26th TIME: 1pm ET If you are thinking of using the leading NoSQL database in a project, learn just how easy it is to get started with...
by Tim.Callaghan | Sep 10, 2013 | MySQL
In talking to existing MongoDB users and TokuMX evaluators, I’ve often heard that the performance of MongoDB is very good as long as your working data set fits in RAM. The story continues that if your working data set grows to be larger than the RAM on your...
by Tim.Callaghan | Sep 5, 2013 | MySQL
We’ve been hard at work on TokuMX since it’s initial release just over 2 months ago. Today we released TokuMX v1.2 which includes Hot Backup in the Enterprise Edition. Hot Backup allows users to create a backup of a running TokuMX primary or secondary...
by Zardosht.Kasheff | Aug 15, 2013 | MySQL
A common MongoDB tip is to create short field names to save storage space. Because MongoDB does not compress its data on disk and stores field names in each document, using longer field names leads to bigger documents which leads to more storage space usage. The...
by Leif.Walsh | Aug 7, 2013 | MySQL
Recently, we’ve seen a few people ask us about building TokuMX from scratch. While it’s best if you just use the binaries you can get from us (they have all the right optimizations, we’ve tested them, and we can interpret coredumps they generate), we...
by Zardosht.Kasheff | Aug 2, 2013 | MySQL
On Wednesday night, the Boston MongoDB User group was kind enough to have me speak about TokuMX Internals. I spoke about Fractal Tree® indexes and the technical reasons behind the benefits they provide to MongoDB applications. Although the talk mostly references...
by Stephane Combaudon | Aug 1, 2013 | Insight for Developers, MongoDB, MySQL
For people used to relational databases and doing MySQL database design, using NoSQL solutions such as MongoDB brings interesting challenges. One of them is schema design: while in the relational world, normalization is a good way to start, how should we design our...
by Leif.Walsh | Jul 23, 2013 | MySQL
Since we released TokuMX, one of the most frequent requests has been for a migration tool. TokuMX has a completely different storage format than MongoDB, which means that you have to actually move all of your data out of MongoDB and into TokuMX, you can’t just...
by Zardosht.Kasheff | Jul 22, 2013 | MySQL
A lot is said about the differences in the data between MySQL and MongoDB. Things such as “MongoDB is document based”, “MySQL is relational”, “InnoDB has a clustering key”, etc.. Some may wonder how TokuDB, our MySQL storage engine, and TokuMX, our MongoDB product,...
by Zardosht.Kasheff | Jul 15, 2013 | MySQL
Before creating a unique index in TokuMX or TokuDB, ask yourself, “does my application really depend on the database enforcing uniqueness of this key?” If the answer is ANYTHING other than yes, do not declare the index to be unique. Why? Because unique indexes may...
