Since its inception our flagship Infobright Enterprise Edition analytic platform (now renamed IEE MySQL Edition) has leveraged MySQL as its underlying data store. This week, we are excited to release our new IEE Postgres Edition. This addition to our analytics platform portfolio is based on the PostgreSQL storage engine.
There were lots of reasons to introduce support for PostgreSQL not the least of which was giving our customers and OEM partners a choice of IEE that best leverages their skill sets, corporate standards, and licensing requirements.
Support for Postgres is not the entire story for this release. IEE Postgres Edition is built on a completely new architecture designed to accommodate not only new storage engines but also puts in place the infrastructure to offer multi-machine and other high performance capabilities in subsequent releases. This new architecture is the culmination of two years of research and development based on customer input and market trends. It leverages Infobright’s expertise in machine-generated data advancing it to support Web-scale analytics for the Internet of Things.
In this new architecture, Infobright’s technology, called IB Core, is encapsulated as a process in a multi-process architecture. Communication with the storage engine is achieved through the IB Adapter and IB Interface. The new architecture differs markedly from the current IEE MySQL single-process architecture. While this monolithic architecture served the market for a MySQL-based ad hoc analytic platform, the architecture provides five key advantages:
- Isolation from the underlying data storage engine
- Better control over memory management between IB Core and PostgreSQL
- More control over process management between IB Core and PostgreSQL.
- The ability to support additional storage engines in the future, including NoSQL stores.
- Putting in place the foundation for multi-machine scaling, real-time data loading and high availability and disaster recovery options.
In addition to our requirement to evolve the architecture to accommodate different storage engines, we had the additional goal to maintain functional and performance parity across our entire analytics platform portfolio. With the release of IEE Postgres Edition, I am very pleased to say that these goals were met and validated through an extensive beta program. Of course, differences in data types and sizes, as well as supported character set differences between MySQL and Postgres, are inherited in IEE. A migration utility is available to help existing IEE MySQL Edition customers who choose to move to the IEE Postgres Edition.
Choosing between IEE MySQL and Postgres Editions
Both of our IEE editions are similar in functionally and performance. When considering which platform is right for your business, consider these points:
- Your company’s database standards and skill set
- Are you porting an existing MySQL or Postgres database?
- Does your company have an investment in third party tools for either MySQL or Postgres?
- Do you need flexible licensing options?
More to come
We are really excited about this new release. The new architecture is a giant step forward and is designed to continue the evolution to a high performance analytic platform supporting Web-scale analytics for the Internet of Things. Expect to see many other exciting new capabilities released over the upcoming months, including multi-machine query capabilities, new advanced analytics features like Approximate Queries, integration with third party data sources, and high performance real-time data loading. MySQL customers will also be pleased be pleased to learn that IEE MySQL Edition will be migrated to this new architecture later this year, ensuring access to all of the new capabilities planned for IEE.Subscribe to Blog