{{announcement.body}}
{{announcement.title}}

Integrating With SaaS Applications — An Introduction

DZone 's Guide to

Integrating With SaaS Applications — An Introduction

In this series introduction, we set the stage for an explanation of how Red Hat seeks to integrate with SaaS applications.

· Cloud Zone ·
Free Resource
Since introducing the first architecture blueprint focused on omnichannel integration, we've been looking at how to integrate with Software as a Service (SaaS) applications.
It's an interesting challenge in that we've been given the mission of creating architectural content based on common customer adoption patterns. That's very different from most of the traditional marketing activities usually associated with generating content for the sole purpose of positioning products for solutions. When you're basing the content on actual execution in solution delivery, you're cutting out the chaff. What's that mean?   

It means that it's going to provide you with a way to implement a solution using open source technologies by focusing on the integrations, structures, and interactions that actually have been proven to work. What's not included are any vendor promises that you'll find in normal marketing content. Those promised that when it gets down to implementation crunch time, might not fully deliver on their promises.

Enter the term Architectural Blueprint.  

Let's look at these blueprints, how they're created, and what value they provide for your solution designs.

The Process

The first step is to define what we are focusing on when we talk about integrating SaaS applications.

We've settled on the following to guide our blueprint: "Integrating with SaaS applications means providing your organization with consistent, responsive, and secure access to services, applications, and platforms."

Reasons to integrate with SAAS

This is the launching principle that guides our research into how customers are looking at integrating with their SaaS application landscapes.   

The approach taken is to research our existing customers that have implemented solutions in this space, collect their public-facing content, research the internal implementation documentation collections from their successful engagements, and where necessary reach out to the field resources involved.

What's Next   

The resulting content targets the following three items.        

  • A slide deck of the architectural blueprint for use telling the portfolio solution story.
  • A generic architectural diagram providing the general details for the portfolio solution.  
  • A write-up of the portfolio solution in a solution brief format.  

An overview of the series on integrating SaaS applications portfolio architecture blueprint can be found here:

  1. An introduction
  2. Common architectural elements
  3. Example CRM integration
  4. Example CRM connector integration
  5. Example 3rd-party platform integration
  6. Example processes with 3rd-party platform integration
Catch up on any articles you missed by following one of the links above. Next in this series, taking a look at the common architecture elements used to integrate SaaS applications.
Topics:
architect, architecture, blueprint, cloud, developer, howto, integration, red hat, saas, saas applications

Published at DZone with permission of Eric D. Schabell , DZone MVB. See the original article here.

Opinions expressed by DZone contributors are their own.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}