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:
- You’re Struggling with the Integrator’s Dilemma
- You Have Unintegrated Integration:
- You Thought Cloud = API Utopia
- You Still Have Swivel Chair Integration
- 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.
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.
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!
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:
- Determine if you’re suffering from the “Integrator’s Dilemma”
- Review your Integration Competency Center / Center of Excellence practices
- Do an audit of your cloud applications currently in use
- Dig into Hadoop
- Investigate AWS Redshift other cloud data warehouse/ business intelligence / analytics options
The presentation is embedded below. Feedback welcome!
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
- 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.
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:
- 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.
- 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.
- Create, Edit and Schedule – Citizen Integrators are going to expect to be able to drag, drop and connect.
- 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.
- Extensive Deployment Options – Cloud to Cloud, Cloud to Ground and Hybrid deployments must be supported.
- 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.
- 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.
- 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.
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):