Collaborations in Building Hybrid Cloud Computing and Data Integrations

Post first published by Ravi Dharnikota on LinkedIn.

It’s one thing to create application and data integrations; it’s an even bigger challenge to collaborate with other teams in the enterprise to reuse and repurpose and standardize on what has already been built.

The need for seamless content collaboration is a key ingredient for overall success in app and data integrations, just as it is in app development and delivery. A platform that allows for easy sharing of information between employees is the different between a platform’s adoption throughout the enterprise or becoming shelf-ware.

Some common impediments to collaboration in an integration platform are lack of a lifecycle management of the integration, versioning of these integration pipelines, ability to create from templates, easy sharing of projects and integration assets, and even proper documentation.

Content collaboration is just as important as building robust integrations and it is essential for enterprises to adopt an integration platform where they can create, manage, store and share integrations in the cloud. In innovating the next generation of cloud and big data integration platform as a service (iPaaS), SnapLogic includes the following collaborating features:

PatternsSnap Patterns

Patterns are pre-built, reusable integration pipelines that can be configured through a step-by-step wizard. These pattern pipelines serve as templates for common integration patterns that can be shared and built upon.

Accounts Repository

The first step to creating integrations is to set up endpoint accounts. The challenge is to keep them organized, provide the right authorization and make it reusable. The Accounts repository let’s you create and store account access information for your Snap connections, which can be shared and reused during development, or assigned to a service level account in the production.

Projects

Within the SnapLogic platform, Projects are logical groupings of pipelines, files, accounts, tasks, Snaplexes and possibly Snap Packs. These projects can be shared with anyone within the organization with varying permission levels.

Permissions

Self-Documenting Integrations

Documentation is key to collaboration, yet so often ignored. SnapLogic makes it easy by self-documenting each data flow pipeline. Each pipeline can be printed or downloaded as a document with the details of the Snaps and configuration of the pipeline including when it is scheduled to run.

Self-Documenting-Integrations

Sharing Assets

Each SnapLogic pipeline is represented as a JSON document that can be downloaded and checked into a version control repository if so desired. Projects can be exported. Exporting a project sends all pipelines, files and tasks to a .zip file.

Exporting

 

Pipeline Versions

The SnapLogic Elastic Integration Platform also provides the capability to version pipelines within the designer. Pipeline versions let you easily replace an existing pipeline with a newer one, or rollback to a previous version in the event something went wrong.

Pipeline versions

Pipelines can also be copied, moved, exported and imported.

Pipeline commands

I also posted this overview on LinkedIn. Comments or questions are welcome there or here. You can learn more about the SnapLogic enterprise iPaaS in this technical whitepaper and be sure to check out our demos here.