For the past couple of quarters, Infobright has been MySQL’s partner of choice for larger data warehousing applications. Infobright’s stated business metrics, and I quote, include:
> 50 Customers in 7 Countries
> 25 Partners on 4 continents
A vibrant open source community
+1 million visitors
Approaching 10,000 downloads
2,000 active community participants
These may be compared with analogous metrics Infobright offered in February.
Infobright has also made or promised a variety of technological enhancements. Ones that are either shipping now or promised soon include:
- Routing all SQL through the Infobright Knowledge Grid rather than the generic MySQL engine. I forgot to double-check whether this is truly all SQL or just most, e.g., whether such SQL 2003 OLAP extensions as MySQL supports are included.
- Being able to query all data even when a load is going on. Specifically, Infobright will do versioning rather than relying on the current table-level locking scheme.
- Getting certified for Sun OpenStorage, which brings flash memory goodness and an associated speed-up.
Infobright is also previewing what it calls SSA (Simplified Scalability Architecture), which it plans to ship late this year. The essence of Infobright SSA is scale-out beyond a single server. Data access will still be shared-everything. Infobright stresses that performance is generally not disk-bound and — which sounds odd — not affected by the size of the database. Hence it doesn’t see any reason for a shared-nothing configuration.
If ACID compliance is on the roadmap, I missed it. (Edit: See the comments below — Infobright now boasts ACID compliance.) I know of at least one case in which Sun/MySQL suggested using a combination of the Infobright and MyISAM engines for an update-heavy data warehousing environment, but that configuration isn’t going to give ACID compliance either.