anchor.diff:  
   In addition to grouping multiple components within an application, you can also use the *Topology* view to connect components with each other. You can either use a binding connector or a visual one to connect components.
   
  -When an application is connected to a service using a binding connector a `ServiceBindingRequest` is created with the necessary binding data. After the request is successful, the application is redeployed. A binding connection between the components can be established only if the target node is an Operator-backed service. This is indicated by the *Create a binding connector* tool-tip which appears when you drag an arrow to such a target node.
  +A binding connection between the components can be established only if the target node is an Operator-backed service. This is indicated by the *Create a binding connector* tool-tip which appears when you drag an arrow to such a target node.
  +When an application is connected to a service using a binding connector a `ServiceBindingRequest` is created. The *Service Binding Operator* controller then uses an intermediate `Secret` to inject the necessary binding data into the application `Deployment` as environment variables. After the request is successful, the application is redeployed establishing an interaction between the connected components.
   
  -A visual connector establishes only a visual connection between the components, depicting an intent to connect. No interaction between the components is established. If the target node is not a binding Operator-backed service the *Create a visual connector* tool-tip is displayed when you drag an arrow to a target node.
  +A visual connector establishes only a visual connection between the components, depicting an intent to connect. No interaction between the components is established. If the target node is not an Operator-backed service the *Create a visual connector* tool-tip is displayed when you drag an arrow to a target node.
   
   == Creating a visual connection between components
   
  -You can connect a MongoDB service with a Node.js application visually as follows:
  +You can depict an intent to connect application components using the visual connector.
  +
  +This procedure walks through an example of creating a visual connection between a MongoDB service and a Node.js application.
   
   .Prerequisites
   
  
positive.code: A DB instance is now deployed in the *Topology* view.
  
  . In the *Topology* view, hover over the Node.js component to see a dangling arrow on the node.
  . Click and drag the arrow towards the *db-demo-postgresql* service to make a binding connection with the Node.js application. When an application is connected to a service using the binding connector a `ServiceBindingRequest` is created and the *Service Binding Operator* controller injects the DB connection information into the application `Deployment` as environment variables using an intermediate `Secret` called `binding-request`. After the request is successful, the application is redeployed.
  +
  image::odc-binding-connector.png[Binding Connector]
  
negative.code: ====
  
  
  [NOTE]
  ====
  Currently, a few specific Operators like the *etcd* and the *PostgresSQL Database* Operator's service instances are bindable.
  ====
  
  You can establish a binding connection with Operator-backed components.
  
  This procedure walks through an example of creating a binding connection between a PostgreSQL Database service and a Node.js application. To create a binding connection with a service that is backed by the PostgreSQL Database Operator, you must first add the Red Hat-provided PostgreSQL Database Operator to the *OperatorHub* using a backing `OperatorSource`, and then install the Operator.
  
  .Prerequisite
  * Ensure that you have created and deployed a Node.js application using the *Developer* perspective.
  * Ensure that you have installed the *Service Binding Operator* from *OperatorHub*.
  
  .Procedure
  . Create a backing `OperatorSource` that adds the PostgresSQL Operator provided by Red Hat to the *OperatorHub*. A backing `OperatorSource` exposes the binding information in secrets, ConfigMaps, status, and spec attributes.
  .. In the *Add* view, click the *YAML* option to see the *Import YAML* screen.
  .. Add the following YAML file to apply the `OperatorSource`:
  +
  