CIOs are Getting SMACT: #Social, #Mobile, #Analytics, #Cloud, #IoT

Check out this Infographic from SnapLogic – Why Are CIOs Getting SMACT?
[Infographic] Why Are CIOs Getting SMACT?

Influential Business Intelligence Blogs

In(tegrate) the Clouds was named as one of the 23 most influential business intelligence blogs today by Justin Heinze at BI Software Insight.  It’s a great list to be a part of – thanks Justin! It’s also helpful to get the Twitter handles of all of the bloggers.

Here’s the list, in no particular order I don’t think:

  • TechnoSocial Blog
  • Smart Data Collective
  • BI Analysis
  • In(tegrate) the Clouds
  • Upstream Info
  • AllformZ BI Blog
  • Forbes Blog: Bruno Aziza and The Tribulations of an Analytical Mind
  • B-Eye Network Channel: BI & Integration – Colin White
  • Business Intelligence
  • Business Intelligence and Cultural Transformation: Peter James Thomas
  • Key 2 Consulting
  • Business Intelligence Products and Trends and B-eye Network Blog: Barney Finucane
  • The Data Doghouse
  • Meta Analysis
  • Ms. SQL Girl
  • Business Analytics News
  • Business Intelligence: Process, People, and Products
  • Decideo.fr: Francophone Community of Business Intelligence Users
  • BI Scorecard
  • TDWI: Business Intelligence Portal
  • Ventana Research: Perspectives by David Menninger
  • James Kobelius’ Blog

You can read the entire post with all of the links here. You can read more of my posts about cloud data and application integration on the SnapLogic blog.

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.

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.

&

Reinventing IT in the Digital Enterprise

PWC has launched a New IT Platform which has 5 key components:

  • IT Mandate
  • Process
  • Architecture
  • Organization
  • Governance

When it comes to the New IT Platform Architecture, PWC calls for an Integration Fabric. It’s a term I hear more and more from forward-thinking enterprise IT leaders who are looking for increased agility and the ability to rapidly connect data, applications and APIs.

Integration Fabric

This video features Mike Pearl, Principal from PwC’s Silicon Valley Practice, providing a good summary of the changing role of the CIO in today’s marketplace.

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):

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.


RSS In(tegrate) the Clouds RSS

  • An error has occurred; the feed is probably down. Try again later.

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

Join 4,806 other followers

Follow Me on Twitter


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

thoughts on web services people pay for

hireED4HigherEd

studentforce .... designed by students for students

Follow

Get every new post delivered to your Inbox.

Join 4,806 other followers

%d bloggers like this: