What’s Next for Data Analysis? Part I

I’m commonly asked this question in a variety of circles and on several continents. I consider it one of the more interesting aspects of my job to have these types of predictive, future-oriented conversations with a wide variety of people: customers, partners, technologists, journalists, analysts, consultants, entrepreneurs, financial analysts, researchers, and so on. So, I sat down recently to simply document my answer to the question “What’s Next for Data Analysis?” Here are my thoughts.

I believe the next few years will be an amplified continuation of what we've seen in the past few years, albeit with a severely web-focused, any-client device emphasis. Many of the patterns I’ll cite have been underway for some time; it’s just that the more simple and affordable ability to implement them has only recently caught up with the ambition.

Here goes. Next-generation data analysis will . . .

. . . embrace the rise and use of “big data” for nearly any size organization. I’ve long said that big, distributed data is not limited to big enterprise and many companies will find valuable insight because they can sift through it all to find new answers.

. . . require a more varied set of "analytics" - from responsive and unstructured to predictive and highly-structured. There are many ways to use data productively. Sometimes understanding the past is the most important point. Sometimes being able to predict the future, based on the patterns of the past, is required. The lines here will blur and more organizations will need both and many types in between.

. . . demand greater use of low latency analysis, which decreases the time between a business event occurring, its analysis, and a decision that is based on it. Sometimes this is referred to as “real-time BI” and other times “streaming analytics”. Let’s just call it useful and necessary in more environments each year.

. . . be untethered from traditional client computing network practices. I’ll repeatedly say “analytics anywhere”, which means purely web-based, open standards-aware, (multi-) thin client architecture. That’s a mouthful, but it needs to be the starting point for business intelligence system design (and this is where the mega-vendors’ mostly aged architectures fall short, btw). The most appropriate analytic experience should be deliverable to any device, because both the thin client or native mobile front-end application (where necessary) and the back-end (web) services understand and adapt. More users will expect this every year.

The combination of these clear patterns and trends is surely driving our product and technology roadmap at Jaspersoft. It’s also positively impacting our work with our far-flung community, where so many of our ideas become grounded. Internally, we talk about speeding the movement of “data to dashboard” so the user has the advantage of working with timely and relevant data, presented elegantly and in the proper context. This is our central thought. If you’re interested in learning more about the analytics landscape, from Jaspersoft’s perspective, we’ve published this white paper.

Next post, I’ll describe the recent BI and data management technologies that stand the most to gain as these shifts occur. In the meantime, let me know what you think.

Brian Gentile
Chief Executive Officer
Jaspersoft

Survey Results Point to the Future of Java and MySQL

I’ve been enthralled with Oracle’s acquisition of Sun since the day it was announced, because of what it represents to the foundation of open source software. My very first blog post on this matter, in April of last year, focused on the hearts and minds of the developer, in this case through two of Oracle’s most important acquired assets: Java and MySQL. My concluding remark was “stay tuned”.

Now we fast-forward more than one year. The deal is (finally) concluded and things are settling, right? Not taking anything for granted, I commissioned a survey of Jaspersoft’s substantial registered community members (numbering more than 130,000 at the time of the survey, April 2010, but now at 150,000). Because nearly 70% of Jaspersoft’s community is comprised of software developers (substantially using Java, MySQL and related tools), we felt our findings could be important. And, indeed, they did not disappoint.

We asked the Community about their planned future use for Java and MySQL versus competing technologies and products. We asked them about the expected pace of innovation for these two products and if they believe the community processes would be maintained. In short, we gained a capsule of information regarding the likelihood that these two foundational technologies would remain relevant, or become more so. Here’s a summary of our findings:

• 43 percent of respondents believe MySQL development and innovation will improve under Oracle;
• 80 percent of respondents believe the Java process will improve or stay the same;
• The most popular alternative to MySQL cited by respondents who said they planned to switch databases away from Oracle, is PostgreSQL. But only 5% indicated they would switch.
• 59 percent of survey respondents were not aware that Oracle reorganized and established a completely separate MySQL business unit from the Oracle’s traditional RDBMS business, which includes separate and dedicated engineering, professional services, sales and marketing.

So, it seems that not only is Oracle’s stewardship and ownership of these critical open source products safe for now, but it could lead to a resurgence for Java and even greater success for MySQL. We considered these findings surprising and hopefully good for open source software overall.

You can find our press release, announcing these findings here. And, you can find a complete copy of the survey results white paper here. You can imagine, given my investment of time on this topic, that I’m interested in your thoughts and comments.

Brian Gentile
Chief Executive Officer
Jaspersoft