✕

Integration is critical for digital initiatives, and it's not easy to implement. And what makes it worse is the industry shortage of technical skills. Coupler addresses these issues by making it easier and faster to create and deploy integration flows. It's low-code approach allows less-skilled developers to do the work, expanding your talent pool for integration. At the same time, Coupler's containerized, microservices-based architecture provides the deployment flexibility and scalability that your digital strategy needs. Supported deployment models are bare metal, docker on premise, docker on Cloud.

Coupler solves integration problems quickly with a low-code builder and scalable microservice-based deployment. With Coupler, you:

  • Create flow-based integrations as APIs using a visual diagram and configuration wizards.
  • Deploy flows into Coupler's containerized runtime.
  • Securely manage integration credentials in Coupler's built-in identity vault.
Why
Coupler?
Improved developer experience
The low-code / no-code approach to building Microservices provides a simplified experience to developers. It allows them to swiftly develop Microservice-based applications across a range of platforms, including the web, mobile, IoT, wearables, and more.
Failsafe integration changes
Integration flow management with flow versioning allows you to tweak a flow while it’s still running. You can also test each change multiple times without any effect on the original integration flow.
Easy-to-use dashboard
A user-friendly, visual dashboard gives a clear picture for each integration flow – for yourself, for your colleagues, or for any other individual who wants to know more about a specific flow than just the name.
Interoperability
Achieve secure and seamless interoperability via protocol conversion. Coupler also offers REST/SOAP, SSL & TLS, and IoT protocol support.
Increased system observability
Observe how they use your product through visibility on how Microservices are used through log analytics and transaction monitoring. Develop and quickly deploy new features to modify your solution as per their needs.

Coupler features and functions

Coupler is built to fit cleanly into modern cloud-native solution architectures. From one central console, you can control and deploy to Coupler runtimes spread across multiple cloud environments and multiple clusters. It can serve in the role of a central integration server handling flows for several applications, or a single microservice application with deployment of one or two flows. You can have one or more instances of Coupler with respective flow deployments as needed for your application packaging and scaling.

Login
The login page is an entry page to Coupler that requires a username/email and password to authenticate and proceed to the Coupler's internal pages.
Dashboard
The dashboard page displays the list of flows with quick actions such as create new flow, control, savepoint selection, navigation, and flow search, as well as quick information such as flow name, package name, description, flow status, and flow information. It also provides quick access to environment variable windows.
Create new flow
Create new flow window is used to create a new flow by providing flow properties such as flow name, description, flow type, default exception and package.
Flow canvas
The purpose of the flow canvas page is to design, save, validate, commit, and deploy/undeploy the flow. Whereas the canvas page contains a left panel, a flow design area, and a property panel. The left panel contains Flows and Nodes tabs for selecting flows and nodes to design flows. The Flows tab contains a list of packages that have flows, while the Nodes tab contains a list of categorized nodes. The goal of the design area is to create a flow. The property panel can be used to configure the flow and node properties. There are options to export, import, and delete the flow. Flow developers can also use save points to navigate to any other committed versions of the same flow.
Variable creation
The variable creation window has two tabs: Environment and Flow. The Environment tab allows the user to create environment variables that are accessible throughout the product environment, and the Flow tab allows the user to create flow variables that are only accessible within the flow version.
Flow validation
Flow validation validates the data, type, and schema configured in the flow, as well as the flow creation rules. Validation will fail if there is a rule violation, data, type, or schema mismatch; otherwise, the flow will be validated successfully.
Flow info
Flow information is used to consume the configured Coupler endpoint, which contains HTTP method, Endpoint URL, Request header, and Request body with schema.
Coupler Integration Flow Designer

Coupler Integration Flow designer helps to create, validate, version and deploy the integration flow using a flowchart based visual diagram. Flow designers can configure the integration flows to execute suitable error handling actions depending upon the type of errors.

Coupler Runtime

A lightweight runtime for the integration flows which identifies the right flows to execute based on the incoming request and resolves any mappings done in the inputs using flow as the blueprint.

Built-in Identity Store and Management

Integrated Identity store and access management lets administrators authorize who can act on specific resources, giving you full control and visibility

Connector Framework

Provides an SDK to develop your own connectors to proprietary systems and data formats.

  • Visual Paradigm for flow design
  • Extensive palette of integration flow functions
  • Design time validation of flow consistency and executability
  • Built-in flow versioning and deployment management
  • Hot deployment of integration flows
  • Inbound and Outbound support for REST/SOAP over HTTP/SSL/TLS, File and IoT protocols.
  • Protocol conversion between XML and JSON
  • Error handling with flows, with optional retry submission for flows that have failed
  • Hybrid cloud & multi-environment support – on Bare metal, Docker Containers on Bare Metal, Docker Containers on the top three Cloud services AWS, Azure & GCP.
  • Transaction commit and rollback using compensation calls
  • Flexible log masking policies for secure logging

You may also like

IoT services
Microservices
Legacy modernization
Torry Harris Integration Solutions api integration governance
API and integration governance
Hybrid integration
Data integration
Application integration & system integration
‹ ›
Deplomatic
RepoProTM
Copyright © 2022 Torry Harris Business Solutions
Footer Logo
›