Posts Tagged 'Cloud integration'

[Infographic] Cloud Integration Drivers and Requirements

Here’s an an infographic from SnapLogic that reviews some the drivers and requirements for cloud-based integration, also known as Integration Platform as a Service (iPaaS), as well as reasons why legacy technologies won’t be able to keep up with the need for speed.

Avoiding Same Old Same Old (SO SO) Integration

I recently presented to the San Francisco data management association (DAMA) on The Impact of SMACT on the Data Management Stack. The presentation reviewed what we call the Integrator’s Dilemma, which is faced when legacy integration tools are no longer effective in the new world of Social, Mobile, Analytics, Cloud Computing and the Internet of Things (SMACT) and summarized some of the drivers for changes to the modern data management stack. Check out the SnapLogic blog post for a review of the top 5 changes.

When it comes to avoiding Same Old, Same Old (SO SO) integration, the 5 recommendations are:

  1. Determine if you’re suffering from the “Integrator’s Dilemma”
  2. Review your Integration Competency Center / Center of Excellence practices
  3. Do an audit of your cloud applications currently in use
  4. Dig into Hadoop
  5. Investigate AWS Redshift other cloud data warehouse/ business intelligence / analytics options

The presentation is embedded below. Feedback welcome!

8 Requirements for Citizen Integrators

Search “IFTTT for the Enterprise” and you’ll see that almost every week now there’s a new cloud service/vendor being launched that has cracked the code of balancing data integration simplicity with power. Search “Data Preparation” and you’ll see a new category of vendors that are now positioning themselves as ABETL (Anything But ETL).  You even see SAP embracing simplicity, but many long-time customers and pundits certainly see that as mission impossible.

I wrote a post last week about the rise of the Citizen Integrator on the SnapLogic blog now that “simplicity is the new black” in the new world of DIY data access, integration and management.  Here are a few requirements that I think are going to be essential ingredients:

  1. Single Sign On– If you want more people using the tool, it’s going to have to be as easy to access as other cloud applications.
  2. Cloud-Based Design Environment – Many of the integration tools out there continue to rely on eclipse-based developer tools or last generation’s on-premises tools. These are hardly going to attract the new breed of Citizen Integrator.
  3. Create, Edit and Schedule – Citizen Integrators are going to expect to be able to drag, drop and connect.
  4. Broad Connectivity – Maybe this goes without saying, but integration tools must be able to connect to cloud and on-premises applications, databases, files, and big data sources.
  5. Extensive Deployment Options – Cloud to Cloud, Cloud to Ground and Hybrid deployments must be supported.
  6. Configurable, Re-Usable Patterns – Don’t make me re-invent the wheel. Give me some starter templates and allow me to share them with others.
  7. Mobile Monitoring – There’s an app for that! As Salesforce1 now allows me to run my business on my phone, integration should also be turned into an app for specific use cases.
  8. Online Training, Tutorials, Community – It’s no secret that SaaS and community go hand and hand. DIY developers are going to want to find what they need with a few clicks.

&

7 Things You Should Know About SnapLogic’s Elastic Integration Platform

In a series of recent posts on the SnapLogic blog, I’ve been reviewing the primary requirements of a modern integration platform. In this post I outlined some of the key principles behind SnapLogic’s Elastic Integration Platform, as well as the most popular posts on the blog. (Not surprisingly, 3 of the 5 most popular posts were written by the company’s Chief Scientist.)

The presentation below provides an overview of 7 things you should know about SnapLogic’s elastic integration platform as a service (iPaaS):

SnapReduce: Cloud Integration and Big Data

For 5+ years this blog has focused primarily on the topic of integrating cloud applications like Salesforce.com, Workday, ServiceNow, Zuora, etc. with each other and with on-premises applications like SAP and Oracle. Occasionally I’ve written about the shift to cloud-based business intelligence tools and platforms, but it’s been mostly all things software as a service (SaaS) and integration platform as a service (iPaaS).

Thanks primarily to YARN and some of the advances in the Hadoop 2.0 platform, this week SnapLogic announced SnapReduce 2.0. Cloud application integration has expanded to big data integration. Here’s SnapLogic’s Chief Scientist Greg Benson discussing the news.

Cloud Application, Analytics and Integration Drivers and Barriers

Last week I hosted a webcast that reviewed the results from a recent SnapLogic TechValidate survey on cloud integration. You can download the complete results of the research here. The webcast also featured a deep dive demonstration of the SnapLogic Integration Cloud. I’ve embedded the recording below.

Why the ESB is the Wrong Approach to Cloud Integration

This week Maneesh Joshi from SnapLogic posted an article on Wired Insights called: Why Buses Don’t Fly in the Cloud: Thoughts on ESBs. It’s a pretty deep post, summarizing the vision of a services oriented architecture (SOA) and why the concept of the enterprise service bus (ESB) has reached its limits in the era of Social, Mobile, Analytics, Cloud and the internet of Things (SMACT). Here are a few snippets:

“Long implementation cycles, inability to absorb change, and high costs have made it difficult for these ESB solutions to keep up with fast evolving business requirements and often resulted in unmet expectations.”

“The ESB as an agile integration layer has been exposed as the long pole in project plans and customers are looking for alternatives.”

“On-premise ESBs or cloud integration platforms that are natively XML-based but apply translations to JSON at its extremities to keep up are going to fall short in the world of SMAC.”

“REST and JSON together are increasingly replacing SOAP and XML, making ESBs less relevant in today’s enterprise SMAC architecture.”

“Sticking with legacy technologies such as ESBs will only hamstring organizations from innovating rapidly and capitalizing on emerging opportunities.”

Do you agree? Do you see integration platform as a service (iPaaS) as complementary or a long-term replacement of the ESB as more and more of the applications and platforms are delivered in the cloud?


Enter your email address to subscribe to this blog and receive notifications of new posts by email.

Join 5,072 other followers

Follow Me on Twitter


Sheffield View

Trying to keep up with Big Data Vendor Landscape

A Passion for Research

Focusing on CRM, cloud computing, ERP and enterprise software

SnapLogic Blog

Thoughts on Integration Platform as a Service (iPaaS), Analytics and the SnapLogic Integration Cloud

Learning by Shipping

products, development, management...

Laurie McCabe's Blog

Perspectives on the SMB Technology Market

SaaStr

Getting From $0 to $100m ARR Faster. With Less Stress. And More Success.

Follow

Get every new post delivered to your Inbox.

Join 5,072 other followers

%d bloggers like this: