In Part I, I talked about a couple of reasons why cloud BI hasn’t gone mainstream yet – the inherent complexity of BI systems and the amount of data produced daily. Then I presented a secure way for data to remain in place but your BI to move into the cloud. (web services-based SOA broadcast services, essentially querying data that exists behind your corporate firewall from the cloud). Today let’s weigh the risks vs. rewards of moving your BI to the cloud.
Choosing a Cloud BI Vendor
Do you stick with your familiar BI software as it adapts to a SaaS model or go with a newcomer offering true SaaS? Be sure to carefully consider your business requirements and go with a vendor that meets them. You may risk going with a smaller vendor, but you are more likely to get the BI deployment you want.
Certainly evaluate the long-term cost of ownership – cloud BI may be more affordable at the outset and allow you to avoid the capital expenditure approval process, but will it cost more in the end? The reward of a quick implementation and “easy out” may be worth the risk of higher long-term cost and may lead to additional benefits, like allowing you to scale your BI to more users throughout the organization faster.
Sticking with an in-house BI deployment results in your IT team spending time to set up, tweak, maintain, and debug servers – time that could be better spent elsewhere…
I bet when you were building your Business Intelligence application, it never occurred to you that your users would be so demanding. After all, you’ve managed to provide them reports and charts containing all the data they entered into the system. Now, in addition to the data in your internal systems, they’re asking you to add in data from other sources that you have no control over. This is actually the latest trend and I’m convinced it’ll get worse before it gets better. In the old days, you could just tell them you don’t have the data and it would cost a lot of money to bring the information feed in-house. But like I said in my previous article on user expectations, your users already have access to this data on their home computers and they expect the same type of information access from the BI systems they use to get their job done.
The good news is that those applications are using something that’s readily available to you — Web Services (WS). The reason this data used to be unavailable in the past is because the producers had no way of giving it to the consumers. They could dump the data into delimited files and email them to you, but what good would that have been?
Awhile back, a bunch of bright people came up with a way to simplify the process and the concept of Web Services was born. By defining the structure of their feeds, producers of information on the internet can give you instant access to all of their data. Generally, Web Services are a combination of Data Feeds and the Data Definition Language (DDL) that describes them called WSDL. WSDL is a standard way of telling another program what the data feed looks like by defining the input parameters, their format, and the output of the Web Service. To the right is an example of a Stock Quote service provided by www.webservicx.net