added hybrid mode

Author: OlgaPodo

graph/patterns/longRunningOperations.md

@@ -241,3 +241,70 @@ HTTP/1.1 200 OK
 "resourceLocation": "https://graph.microsoft.com/v1.0/storage/archives/987"
 }
 ```
+### Trigger a long running action using the Stepwise Operation
+
+```
+POST https://graph.microsoft.com/v1.0/storage/copyArchive
+
+{
+"displayName": "Image Archive",
+"destination": "Second-tier storage"
+...
+}
+```
+
+The API responds synchronously that the request has been accepted and includes
+the Location header with an operation resource for further polling.
+
+```
+HTTP/1.1 202 Accepted
+
+Location: https://graph.microsoft.com/v1.0/storage/operations/123
+
+```
+###  Trigger a long running action using the Stepwise Operation in hybrid model
+
+The server responds synchronously to POST requests to collections that create a resource even if the resources aren't fully created when the response is generated. The response includes a representation of the incomplete resource that will eventually exist at the URL in the Content-Location header and the Location header with an operation resource for further polling.
+
+```
+POST https://graph.microsoft.com/v1.0/storage/databases/
+
+{
+"displayName": "Retail DB",
+}
+```
+
+The API responds synchronously that the database has been created and indicates
+that the provisioning operation is not fully completed by including the
+Content-Location header and status property in the response payload.
+
+```
+HTTP/1.1 202 Accepted
+Content-Location: https://graph.microsoft.com/v1.0/storage/databases/db1
+Location: https://graph.microsoft.com/v1.0/storage/operations/123
+{
+"id": "db1",
+"displayName": "Retail DB",
+"status": "provisioning",
+[ … other fields for "database" …]
+}
+```
+The client waits for a period of time then invokes another request to try to get the database status.
+
+```
+
+GET https://graph.microsoft.com/v1.0/storage/operations/123
+```
+If resource creation is successful then the server responds with a "status:succeeded" and the resource
+location.
+
+```
+HTTP/1.1 200 OK
+
+{
+"createdDateTime": "2015-06-19T12-01-03.45Z",
+"lastActionDateTime": "2015-06-19T12-06-03.0024Z",
+"status": "succeeded",
+"resourceLocation": "https://graph.microsoft.com/v1.0/storage/databases/db1"
+}
+```

graph/patterns/operations.md

@@ -0,0 +1,70 @@
+# Operations pattern
+
+Microsoft Graph API Design Pattern
+
+ 
+
+### *Operations pattern provides an ability to model a change which impacts multiple resources and can't be effectively modeled using HTTP methods*
+
+<BR>
+
+## Problem
+---
+Sometimes when modeling a complex business domain API designers need to model a business operation which effects multiple resources and needs to be performed as a single unit. Modeling the operation via HTTP methods on each individual resource may be either ineffective or doesn't reflect how it's proccessed by the backend service. In addition the operation may produce an observable side effects.
+
+* *
+
+## Solution
+--------
+
+To address these use cases an API designers may use operational resources such as functions or actions.
+If the operation doesn't have any side effects and MUST return a single instance of a type or collection of instances then the designer SHOULD use OData function.
+otherwise the designer can model operation as an action.
+
+
+* *
+
+
+## Issues and Considerations
+---
+
+ - MS Graph does NOT support unbound actions or functions.
+
+Bound actions and functions are invoked on resources matching the type of the binding parameter. The binding parameter can be of any type, and it MAY be Nullable. For MS Graph, actions and functions must have the `isBound="true"` attribute. The first parameter is the binding parameter.
+
+ - Both actions and functions support overloading, meaning a schema may contain multiple actions or functions with the same name.The overload rules as per the OData [standard](http://docs.oasis-open.org/odata/odata-csdl-xml/v4.01/odata-csdl-xml-v4.01.html#sec_FunctionOverloads) apply when adding parameters to actions and functions.
+  
+ - As Graph only supports bound actions and functions, all must have at least one parameter where the first is the binding parameter. The MUSTS of parameters:
+
+    - Each parameter must have a simple identifier name.
+    - The parameter name must be unique within the overload.
+    - The parameter must specify a type.
+
+ - Graph supports the use of optional parameters. The optional parameter annotation can be used instead of creating function or action overloads when unnecessary. 
+
+ -  API designer **MUST** use POST to call operations on resources.
+                                    | 
+ - Addition of  a new mandatory not nullable parameter to an existing action or function is a breaking change and is not allowed without proper versioning []().
+
+
+## When to Use this Pattern
+
+The operation pattern is well suited to use cases which cannot be modeled as a single HTTP method on a resource and require either multiple round trips to complete a single logical operation or produce one or multiple side effects.
+
+There are related patterns to consider such as
+
+[Long running operation](https://github.com/microsoft/api-guidelines/tree/graph/graph) and [Change Tracking](https://github.com/microsoft/api-guidelines/tree/graph/graph).
+
+
+* *
+
+## Example
+-------
+
+*Provide a short example from real life*
+
+* * 
+
+
+
+