Flex with with traditional Flex Data Services does not stack up as a Real Time Business Intelligence Reporting Tool (BIRT). Some popular BIRT’s on the market now are found here: bi software information. In particular I was given a heads up today by our Vice President here at NYX a question would be coming my way to evaluate Flex as a replacement for Brio, which is currently a BIRT that has not been satisfying and is slated for replacement by something better. Could Flex be the right choice? In this article, I’ll try and do a comparison of the two and show why the traditional approach to targeting the flash runtime with Flex will not do for a real-time BIRT solution.
T first thing is to point out is the Flex API is just a presentation layer. As a presentation layer technology, Flex does not support direct access to databases. This may sound like a disadvantage but in practice it is not. In well-designed applications, the presentation layer (the user interface) is separated from the business layer containing the functionality or business rules of the applications and the data storage. Traditionally, Flex Data Services enables Flex and Flash to interact with Web Services, HTTP Services, and Remote Objects.
A web service supports machine-to-machine interaction over a network through an interface described in a machine-processable format called WSDL. Other systems interact with the web service in a manner prescribed by its wsdl description.
An Http service is a simple servlet that handles http requests to a URL and responds with XML data, which flex can handle in an object-oriented way.
A remote objects is a data object in the Flex applications classpath. It’s important to note this could be rendered by any platform, including the .NET Framework and not just Java.
As was mentioned previously, the best practice in software design is to separate the presentation layer from the business layer to facilitate agile development process. The Flex API dominates other API’s in this regard, but also promises any distributed application browser transcendence. Also, with Flex Builder 3 distributed applications become desktop applications when they are built on the Adobe AIR API. Customers are now expecting a more attractive and sophisticated look and feel, faster delivery, and less fuss with cross-browser compatibility made possible by targeting the Flash runtime and the less known but also very powerful AIR runtime for desktop applications.
Despite all these advantages, the methods of accessing data in flex have a common shortcoming since they all represent asynchronous and disconnected interaction between the presentation layer in Flex and the business layer. This disadvantage clearly disqualifies Flex Data Services as a possible solution for any real-time business intelligence reporting tool. Any enterprise dashboards for these sorts of systems won’t stand up to a real-time BIRT tool like Brio even if the client-facing components are so much less appealing and difficult to implement.
We’ll find out if the latest generation of data services from Adobe can save the Flash runtime environment from its disconnected, asynchronous shortcoming in the next article, which discusses that technology. But first, as promised, let’s take a closer look at Brio Reports.
This site, a company in McLean Virginia who runs the google words “REPLACE BRIO REPORTS” may serve to show real-time messaging protocols we’re about to discuss in the next article are not only a cool idea, but they’re being put into practice right now in many industries, particularly in the financial industry. The demand for these types of products is growing. It’s exciting to be working in this area.
Also, this tutorial published on Josh’s blog in the last 56 minutes also shows developers are actively pursuing Building a LiveCycle Data Service Application with Spring and Hibernate.