Back in Flexmonster 2.9, we often recommended using Flexmonster Data Server (FDS) when dealing with datasets that got over the 1GB mark. It was optional, but necessary for those who want better performance in certain cases.
With Flexmonster 3.0, this changes.
This release is the result of a long process of questioning our own assumptions, facing technical limitations head-on, and rewriting the core of Flexmonster from the ground up.
This blog post is the first in a series of articles in which we’ll tell you more about each of this release’s features. We’d like to share why we decided to rebuild everything, what changed under the hood, and what you can expect from the new version.
Working on Flexmonster has been our team’s passion for years. The component has proven to be a powerful tool with a wide range of data visualization and analysis features. Our team has constantly looked for customers’ feedback and used it to evolve the component further.
Over time, we accumulated numerous ideas on making a qualitative leap to take reporting to a whole new level. Powered by insights and experience, three years ago, we began rewriting everything from scratch to create Flexmonster 3.0.
