So what's next? You can get see what we are up to in general by looking at our issues list. We cannot do everything at once, but here are the current priorities for Tungsten Replicator 2.0.5.
- Parallel replication speed and robustness. I'm currently working on eliminating choke points in performance (like this one) as well as eliminating corner cases that cause the replicator to require manual intervention, such as aging out logs that are still needed by slaves.
- Multi-master replication. This includes better support for system of record architectures, many masters to one slave, and replication between the same databases on different sites. Stephane Giron nailed a key MyISAM multi-master bug for the last release. We will continue to polish this as we work through our current projects.
- Better installations for more types of databases. Jeff recently hacked in support for PostgreSQL as well as Oracle slaves, and we are contemplating addition of MongoDB support. Heterogeneous replication is getting simpler to set up.
- Filter usability. Giuseppe has a list of improvements for filters, which are one of the most powerful Tungsten Replicator features but not as easy for non-developers to use as we would like. Better installation support is first on the list followed by ability to load and unload dynamically.
- Data warehouse loading. We have a design for fast data warehouse loading that I hope we'll be able to implement in the next few weeks. Linas Virbalas has also been working on this problem along with a number of other heterogeneous projects for customers.
After this build we will... Er, let's get 2.0.5 done first. Suffice it to say we have a long list of useful and interesting features to discuss in future blog articles.