The New Data Integration Requirements

This week SnapLogic posted a presentation of the 10 Modern Data Integration Platform Requirements on the company’s blog. They are:

1. Application integration is done primarily through REST & SOAP services
2. Large-volume data integration is available to Hadoop-based data lakes or cloud-based data warehouses
3. Integration has to support the continuum of data velocities starting from batch all the way to continuous streams
4. Integration is event-based rather than clock-driven
5. Integration is primarily document- centric
6. Integration is hybrid and spans cloud-cloud and cloud-ground scenarios
7. Integration itself has to be accessible through SOAP/REST APIs
8. Integration is all about connectivity… connectivity connectivity
9. Integration has to be elastic
10. Integration has to be delivered as a service

I’ve embedded the presentation below.

Data Management Requirements for the Enterprise Data Lake

SnapLogic published Eight Data Management Requirements for the Enterprise Data Lake. They are:

1. Storage and Data Formats
2. Ingest and Delivery
3. Discovery and Preparation
4. Transformation and Analytics
5. Streaming
6. Scheduling and Workflow
7. Metadata and Governance
8. Security

The post originally appeared on ITBusinessEdge as a slide show. The company also recently hosted a webinar on Democratizing the Data Lake with Constellation Research and published 2 whitepapers from Mark Madsen.

 

It’s Time to Rethink Integration

Last week SnapLogic posted the company’s mission on their blog, which is focused on accelerating how enterprise integration technology is delivered in the enterprise. The company is growing rapidly and hiring. Here is the their mission statement:

It’s time to rethink integration.
Integrating data and applications with legacy products is slowing down your business.
What you’re running now is no longer running fast enough for today’s business needs.
But what if you could eliminate the pain of integration and get to its promise?
To prioritize outcomes over process.
To enable your enterprise with a modern solution.

With SnapLogic you can.

SnapLogic brings all your data together, at incredible speeds and
with an ease never known before.
Data, applications, and APIs—from any source, anywhere.
Instead of coding, you merely drag and drop intelligent connectors in the cloud.
They fit together seamlessly.
In a snap.

You’ll connect faster and more efficiently, enabling you to become a more agile business.
Whether it’s maximizing investments in big data, or getting new products to market faster.

Whatever your enterprise strategy, SnapLogic gets you there easier and quicker.
And wasn’t that what integration was supposed to do in the first place?
Don’t let your legacy integration solution be your legacy.
It’s time to let go of those old ideas.
It’s time to operate at the speed of modern business.

You can learn more about SnapLogic on the company’s website.

 

 

5 Signs You Need Better Cloud Integration

I recently participated in an online web conference called Cloudcon 2015: Integration and Web APIs where I reviewed 5 signs you need better cloud integration:

1. You’re Struggling with the Integrator’s Dilemma
2. You Have Unintegrated Integration:
3. You Thought Cloud = API Utopia
4. You Still Have Swivel Chair Integration
5. You’re Considering Going Back to On-Prem Due to Diminishing SaaS Returns

It’s a topic I wrote about in this blog post last year. Here’s the recording of the presentation, which also includes an overview of the SnapLogic Elastic Integration Platform and a Q&A session with Vance McCarthy from Integration Developer News.

Hybrid Cloud Integration – Why It’s Different and Why It Matters

This week Carl Lehmann from 451 Research reviewed the trends, best practices and reference architecture for integration platform as a service (iPaaS) and hybrid cloud integration. Here’s the presentation, which also includes an overview of SnapLogic’s Elastic Integration Platform.

The Death of Traditional Integration

Recently I hosted a SnapLogic webinar featuring the company’s co-founder and CEO, Gaurav Dhillon, and industry analyst, author and practitioner David Linthicum called: The Death of Traditional Data Integration. The webinar was very well attended and the discussion was quite lively. I’ve posted sections of the transcript on the SnapLogic blog, you can also listen to the podcast on the company’s iTunes channel, and the slides are now on Slideshare. I’ve embedded the YouTube video below. Enjoy!

[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.

[Infographic] Cloud Integration Drivers and Requirements in 2015 from SnapLogic, Inc.

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!

The Impact of SMACT on the Data Management Stack from SnapLogic, Inc.

Integration Innovation – Why Legacy ETL and EAI Vendors are Struggling

I wrote a post on the SnapLogic blog this week about the wave of innovation that is happening in the data and application integration market and introduced two new data management acronyms (like we need more, I know) – OETL and OEAI:

• Old Extract, Transform, Load
• Old Enterprise Application Integration

There’s no shortage articles (and books) on disruptive innovation and why it’s so hard for on-premises software vendors to transition to the new era of social, mobile, analytics and big data, and the internet of things (SMACT). Here are 10 reasons (some unique and some applicable to all mature technology vendors) why legacy data integration and middleware vendors are struggling to re-invent themselves:

• Cannibalization of the Core On-Premises Business
• Heritage Matters in the Cloud
• EAI without the ESB
• Beyond ETL
• Point to Point Misses the Point
• Franken-tegration
• Big Data Integration is not Core…or Cloud
• An On-Ramp to On-Prem
• Focus and DNA

You can read the entire post here. Let me know if you agree / disagree – I clearly have somewhat of a bias.

Here’s a powerpoint I worked on in 2007 that continues to be appropriate today.

SaaS Cannibalization And Civil War Within from Darren Cunningham

6 Requirements of a Modern Integration Platform

In 2009 I worked with data and application integration guru David Linthicum on a whitepaper called, “What to Look for When Evaluating Cloud Integration Solutions.” The 6 requirements were:

1. True multitenant versus hosted offering
2. Ease of use
3. Try and buy / rapid deployment
4. IT or LOB usability
5. Scalability
6. Vendor viability

While I don’t think I’d change this list too much in 2014, I’ve been putting together a series of posts on the SnapLogic blog summarizing the requirements of a modern integration platform. Now commonly known as integration platform as a service (iPaaS), the 6 primary requirements are:

1. Fully-Functional Cloud-based Service (based on a Software-Defined Architecture)
2. Single Platform for Big Data, Application and API Integration
3. Elastic Scale
4. Built on Modern Standards (REST, JSON)
5. Broad Cloud and On-Premises Connectivity
6. Self-Service for Citizen Integrators

Let me know if you agree or disagree with the list. I’ve embedded a demonstration of the SnapLogic Elastic Integration Platform below if this is an area of cloud computing that is new to you.