This week SnapLogic posted a presentation of the 10 Modern Data Integration Platform Requirements on the company’s blog. They are:
- Application integration is done primarily through REST & SOAP services
- Large-volume data integration is available to Hadoop-based data lakes or cloud-based data warehouses
- Integration has to support the continuum of data velocities starting from batch all the way to continuous streams
- Integration is event-based rather than clock-driven
- Integration is primarily document- centric
- Integration is hybrid and spans cloud-cloud and cloud-ground scenarios
- Integration itself has to be accessible through SOAP/REST APIs
- Integration is all about connectivity… connectivity connectivity
- Integration has to be elastic
- Integration has to be delivered as a service
I’ve embedded the presentation below.
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.
Check out this post by Glenn Donovan: The History of Middleware. From the enterprise service bus (ESB) to the integration competency center (ICC), he has a lot to say about the good, bad and ugly of legacy enterprise application integration (EAI) and extract, transform and load (ETL) technologies. The central theme – it’s about the need for simplicity and speed, which has become even more critical for successful cloud integration deployments. Here are a few noteworthy observations in the post:
On the bureaucracy of the ICC:
“Sure you could build competency centers and “factories” but to this day, such approaches end up creating more bureaucracy, more dependencies and complexity while adding less and less value compared to what a developer can build him/herself with RESTful services/micro-services, and most things one wants to integrate with today already have well defined APIs so it’s often much easier to connect and share data anyway.”
On the ESB:
“Along the way, a problem became obvious. The cost, expertise, complexity and time involved in building such elegantly designed and governed systems frameworks ran counter to building systems fast. A good developer could get something done that worked and was high quality without resorting to using all those WS standardized services and conforming to its structure.”
On the need for a new enterprise platform to replace the legacy ESB:
“I think many are ready to dump all that highly complex and expensive overhead which came along with messaging buses when an enterprise class platform comes along that enables them to do so.”
Simplicity = IT agility:
“This is all coming together now, so you will see growing interest in throwing out the old integration server/message bus architectures in organizations focused on transformation and agility as core values.”
Check out the entire article to understand the author’s point of view. As a veteran of the middleware industry, he’s looking at modern integration platform as a service (iPaaS) vendors like SnapLogic as having: “the potential help IT with the “last mile” of cloud build-out in the enterprise, not just due its features, but rather because of the shift in software engineering and design occurring that started in places like Google, Amazon and Netflix – and startups that couldn’t afford and “enterprise technology stack” – and is now making its way into the enterprise.”
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!