Cloud App Integration .com

We talk with Mike Hoskins, CTO at Pervasive Software, about Hadoop and Big Data

With the digitization of communication has come an exponential increase in data production. But the relational database, still the primary means of data storage for companies around the world, was not designed to handle the volume and types of data created by mobile technology, social networking sites, and internet applications.

Hadoop, a platform for organizing and managing so-called “big data,” emerged from engineers at Yahoo! over five years ago and has since grown into a viable alternative to the relational database. We recently spoke with Mike Hoskins, CTO of Pervasive Software, about Hadoop. Hoskins also runs the Pervasive Innovation Lab, where he and colleagues have been working with Hadoop for several years. Hadoop is now maintained by the Apache Foundation. Read more… »

SnapLogic VP explains how growing number of data sources creates need for specialized integration

As the number data types and applications proliferates, cloud integration vendors recognize that they cannot provide integrations for every possible scenario. Instead, they are creating platforms for third parties to develop and share custom integration services and tools.

We recently spoke with Clark Newby, Senior Vice President of Product Marketing at SnapLogic, about using a marketplace to deliver integration services. SnapLogic launched its SnapStore integration marketplace in April of 2010.

“In the old days you’d have SAP, Siebel, PeopleSoft, maybe an Oracle database, and you’d connect those three or four things and be done,” said Newby. “What we’re seeing is a burgeoning number of data sources.”

The myriad types of data make it difficult for vendors to create a sufficient number of integration options. “You have more narrowly focused SaaS applications, the social media stream—you have more data sources than ever before,” said Newby. “No single company can possibly develop all the different connectors to all these different data sources.”

To meet the demand for specialized integration tools, Newby’s company created a model based on the iPhone App Store. Both SnapLogic and third party developers can create applications designed to perform a specific type of integration, then offer it through the SnapStore for sale and download. As in Apple’s App Store, all applications are subject to approval.

Newby said that while this may limit the number of integration applications available, it ensures quality and functionality. “I see others out there in the market doing more of a craigslist-style marketplace,” said Newby. “That’s not us. Every single snap in the Snapstore uses the same underlying API and a standard open development environment.”

Many integration vendors tap into the integration marketplace model

SnapLogic’s SnapStore was an early entry to the integration services marketplace marketplace. Other companies are beginning to create their own platforms for developing and sharing integration services. This April Pervasive announced Pervasive Galaxy, a development and collaboration platform for the creation of integration services. Pervasive Galaxy combines a service marketplace with tools for chat, revenue sharing, auctioning, and crowdsourcing. Popular ESB provider MuleSoft also announced an integration marketplace for its Mule iON platform.

ALM and the ESB can add functionality to cloud integration scenarios

Application lifecycle management (ALM) and enterprise service buses (ESBs) have long had a part in helping to meet on-premise application integration challenges. But these technologies have a place in cloud-based application integration as well.

We recently spoke with Geoji George, Director of Product Management, Integration Division at Pervasive, about the inclusion of these technologies in a cloud integration tool. Pervasive released a cloud-based version of its Data Integrator v10 this past November that includes an ALM tool and an ESB. Read more… »

On-premise or cloud, choosing an integration tool requires careful consideration

Choosing between a cloud-based integration tool and an on-premise integration tool is an important decision. Many factors must be considered.

We recently talked with Geoji George, Director of Product Management, Integration Division, at Pervasive about that choice. Pervasive released a cloud-based version of its Data Integrator v10 this past November. An on-premise version will be available this spring. Read more… »

As convenient as cloud computing can be, it’s important to remember that the convenience comes from passing on difficulties to someone outside your organization. Problems arise when their difficulty–say, trouble integrating with another third party provider you’ve enlisted–has a direct effect on how you do business. News from today suggests you can prevent these issues such by handling cloud integration early and often.

In a blog post today about cloud silos and integration, David Linthicum advocates doing integration in a step-by-step manner as a cloud-based system is built instead of waiting until after the pieces are in place. Failing to integrate in an iterative way will lead to silos. Siloed systems in a cloud computing environment, Linthicum says, can have worse consequences than siloed sytems on premise.

For in-the-trenches proof of the importance of early integration, consider New Zealand-based nonprofit St. John, whose SaaS CRM integration is profiled as part of a feature article on cloud implementation. St. John IT direct Peter McDowall is quoted in the story as saying, “We focused on integration upfront, but we could have put even more emphasis on it.” McDowall’s company combined Salesforce CRM with existing on-premise software. The organization used Pervasive for cloud data migration.

It may seem like an obvious notion, but taking an iterative approach to integration is not always done. And, given that many systems have been in place for years, it may not always be possible. But as more companies transition to the cloud, the opportunity exists—an opportunity that should be taken—for step-wise integration to occur as new systems are built out.