[OASIS Issue Tracker] (CAMP-207) Assembly to Assembly bindings

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

    [ https://issues.oasis-open.org/browse/CAMP-207?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=62262#comment-62262 ] 

Michael Norman commented on CAMP-207:
-------------------------------------

The use case may be as follows

We need to connect two applications via a messaging service.  The lifecycles of the applications and the messaging services are not coupled.  
Or we need to connect an application to a database, whose lifecycle is independent of the application.
Or indeed we have two applications that consume each other as microservices.

We can imagine have plans (and artifacts etc.) for the database, the messaging service and the applications.
We can represent the requirement to make the connection in the plan. However this is not a requirement to instantiate a component.  It is a requirement to connect to something that is already instantiated. 

The runtime API allows you to identify relationships amongst components, but not amongst assemblies.  However, it seems more intuitive for the relationship to exist amongst assemblies. The way this tends to work is that the assemblies expose endpoints (think of these as URIs, although they needn't be) and other assemblies bind to them. 

> Assembly to Assembly bindings
> -----------------------------
>
>                 Key: CAMP-207
>                 URL: https://issues.oasis-open.org/browse/CAMP-207
>             Project: OASIS Cloud Application Management for Platforms (CAMP) TC
>          Issue Type: Bug
>            Reporter: Michael Norman
>            Assignee: Anish Karmarkar
>
> THis is another placeholder jira to ensure closeout of an issue we have discussed.
> In addition to the hierarchy of instantiation in CAMP-206 we may need a network of bindings to represent relationships amongst assemblies that don't have a coupled lifecycle.  It may be possible to use Operations for this, but more discussion/thought is required.



--
This message was sent by Atlassian JIRA
(v6.2.2#6258)