Tuesday, March 17, 2020

Integrating with SaaS Applications - Example 3rd-Party Platform Integration

integrating with SaaS applications
Part 5 - Example 3rd-party platform integration
The previous article in this series looked at a SaaS CRM connector integration example.

The foundation for this logical diagram was researching a use case where customers were successful with a portfolio solution.

It's a starting point for the generic architectural blueprint that rises from several customer solution that were researched.

Having completed the outline of the blueprint details and the resulting logical diagram elements, it's now time to take a look as specific examples.

In this article we'll continue building the previous examples by sharing how customers are integrating with 3rd-party platforms in their architectures as SaaS platforms.

Blueprint scenarios

As a reminder, the architectural details covered here are base on real customer integration solutions using open source technologies.

The example scenario presented here is a generic common blueprint that was uncovered researching customer solutions. It's my intent to provide a blueprint that provides guidance and not deep technical details.

This section covers the visual representations as presented. There are many ways to represent each element in this architectural blueprint, but I've chosen icons, text and colors that I hope are going to make it all easy to absorb. Feel free to post comments at the bottom of this post, or contact me directly with your feedback.

Now let's take a look at the details in this blueprint and outline the solution.

Integrating with SaaS platforms

The example blueprint shown in figure titled Example: Third-Party Platform Integration outlines how to integrate an existing 3rd-party platform as if it's a SaaS platform.

integrating with 3rd-party platformsAs is often the case, organizational choices in our past have left us with legacy components in our architectures. While sometimes these are simple components to integrate with, we live and learn by applying the same abstractions to our larger platforms that might be hosting a collection of functionality in our organization.

For example, let's assume this image above is making use of a legacy platform hosting a myriad of specialized services that have become impossible to maintain. The amount of interfaces and maintenance has become such a burden that the organization desires to migrate away from the legacy platform, yet cannot at this time due to their dependency on those hosted services.

A logical approach is to segregate the platform as if it's a cloud or SaaS service. This allows for gradual migration of the existing services from the 3rd-party platform at your convenience, including evenutal moves to offsite or cloud-based service hosting. SaaS integration with these services or applications provides many options going forward in managing the architecture.

The blueprint here shows a specific part of the integration, where a front end web connection uses front-end microservices to access integration microservices that manage that generice access to the third-party platform. Note, the security aspects are left in this example to ensure that you remember to include authentication and authorization across your integration landscape.

Implementation details are left up to the reader to quantify as each organizations needs and usage of a specific SaaS integrations with all possible third-party platforms can not be captured in a generic architectural blueprint beyond the above.

What's next

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 and 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 processes and 3rd-party platform integration.